Triple
T23819617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrott |
E589193
|
entity |
| Predicate | openedAsTransitFacility |
P72254
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Arrott, openedAsTransitFacility, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsTransitFacility Context triple: [Arrott, openedAsTransitFacility, early 20th century]
-
A.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
B.
openedAsTransportationCenter
chosen
Indicates that something was inaugurated or began operation specifically in the role of a transportation center.
-
C.
openedAsINDStation
Indicates that a location or facility began operation specifically as a station within the IND (Independent Subway System) network.
-
D.
openedToTransit
Indicates that a route, passage, or connection has been made available or accessible for transit or movement between locations.
-
E.
servesTransitFacility
Indicates that one entity provides service or operational support to a transit facility, such as a station, stop, or terminal.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7ae4f8c8190a92621861cbae2f4 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.