Triple
T34718772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaGuardia Gateway Partners |
E1000850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infrastructure consortium |
C10923
|
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: infrastructure consortium Context triple: [LaGuardia Gateway Partners, instanceOf, infrastructure consortium]
-
A.
infrastructure finance company
An infrastructure finance company is a financial institution that provides long-term funding, credit support, and advisory services for the development, operation, and maintenance of large-scale public and private infrastructure projects.
-
B.
public consortium
A public consortium is a collaborative alliance of multiple public or publicly accountable organizations that pool resources, expertise, and governance to pursue shared goals or projects in the public interest.
-
C.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
D.
infrastructure management company
An infrastructure management company plans, operates, maintains, and optimizes physical assets and systems—such as transportation, utilities, and public works—to ensure their reliability, efficiency, and long-term performance.
-
E.
business consortium
chosen
A business consortium is a collaborative association of independent companies that pool resources, expertise, or capital to pursue shared objectives, projects, or market opportunities while retaining their individual autonomy.
- 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.