Triple
T168750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Transportation Authority |
E3072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public-benefit corporation |
C6
|
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-benefit corporation Context triple: [Metropolitan Transportation Authority, instanceOf, public-benefit corporation]
-
A.
nonprofit organization
chosen
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
-
B.
federally owned corporation
A federally owned corporation is a government-established legal entity that operates commercial or public service activities on behalf of the federal government while retaining a distinct corporate structure.
-
C.
board of trustees
A board of trustees is a governing body of individuals legally entrusted with overseeing an organization’s mission, assets, and strategic direction on behalf of its stakeholders or beneficiaries.
-
D.
company
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
-
E.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.