Triple
T34718773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaGuardia Gateway Partners |
E1000850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public–private partnership entity |
C16096
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: public–private partnership entity Context triple: [LaGuardia Gateway Partners, instanceOf, public–private partnership entity]
-
A.
public–private partnership company
chosen
A public–private partnership company is an entity formed through collaboration between government and private sector organizations to finance, build, and operate projects or services traditionally provided by the public sector.
-
B.
publicly traded partnership
A publicly traded partnership is a business entity organized as a partnership whose ownership interests (units) are traded on public securities exchanges, combining partnership tax treatment with the liquidity of publicly traded stock.
-
C.
partnership structure
A partnership structure is an organizational arrangement in which two or more parties share ownership, responsibilities, risks, and profits according to agreed-upon terms.
-
D.
partnership body
A partnership body is an organized group formed by two or more independent entities that collaborate under agreed arrangements to pursue shared goals, responsibilities, and benefits.
-
E.
public-sector collaboration
Public-sector collaboration is the coordinated effort among government agencies and public institutions, often with private and nonprofit partners, to jointly design, implement, and manage policies or services that address shared societal challenges.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.