Triple
T36959965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MWY |
E914282
|
entity |
| Predicate | underlyingCompanyBasedInState |
P30805
|
FINISHED |
| Object | Illinois |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Illinois | Statement: [MWY, underlyingCompanyBasedInState, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyBasedInState Context triple: [MWY, underlyingCompanyBasedInState, Illinois]
-
A.
associatedWithCompanyHeadquartersState
chosen
Indicates that an entity is connected or related to the U.S. state in which a company’s headquarters is located.
-
B.
hasUnderlyingCompanyIncorporationState
Indicates that an entity is associated with a company whose legal incorporation was carried out in a specified state.
-
C.
underlyingCompany
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
-
D.
stateOfIncorporation
Indicates the legal jurisdiction (state or equivalent) under whose laws an organization or company is formally incorporated.
-
E.
locationOfUnderlyingCompany
Indicates the geographic place where the underlying company is based, registered, or operates.
- F. None of above.
Provenance (3 batches)
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:13 p.m.