Triple
T2857180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRT |
E63229
|
entity |
| Predicate | historicalSystemType |
P32919
|
FINISHED |
| Object | privately operated subway company lines |
—
|
LITERAL FINISHED |
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: privately operated subway company lines | Statement: [IRT, historicalSystemType, privately operated subway company lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSystemType Context triple: [IRT, historicalSystemType, privately operated subway company lines]
-
A.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
B.
historicallyImplementedAs
Indicates that one entity was used or realized as another entity in the past, even if that is no longer the case.
-
C.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
D.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
E.
hasTypeHistory
chosen
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf881bbc81908987317b88b405d0 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.