Triple
T15505031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Football Stadium District |
E379058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special governmental entity |
C2610
|
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: special governmental entity Context triple: [Metropolitan Football Stadium District, instanceOf, special governmental entity]
-
A.
special-purpose governmental unit
chosen
A special-purpose governmental unit is a limited-scope public entity, such as a school district or water authority, created by law to perform a specific governmental function or set of functions within a defined geographic area.
-
B.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
C.
special purpose entity
A special purpose entity is a legally separate organization created by a parent company to isolate financial risk, hold specific assets or liabilities, or conduct narrowly defined activities, often for financing or regulatory purposes.
-
D.
proposed governmental body
A proposed governmental body is a conceptual organization suggested to perform specific public functions or governance roles, but which has not yet been formally established or granted legal authority.
-
E.
specialized institution
A specialized institution is an organization dedicated to a specific field or function, providing focused services, expertise, or education within that domain.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:55 a.m.