Triple
T8876216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line (SEPTA) |
E211290
|
entity |
| Predicate | openedAsSubwaySurface |
P85475
|
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: [Green Line (SEPTA), openedAsSubwaySurface, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsSubwaySurface Context triple: [Green Line (SEPTA), openedAsSubwaySurface, early 20th century]
-
A.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
B.
openedAsUndergroundStation
Indicates that an entity began operation specifically as an underground railway/metro station at the time it was opened.
-
C.
openedAsNYCSubwayStation
Indicates that an entity began operation specifically as a New York City Subway station at the time it opened.
-
D.
subwaySectionOpened
Indicates that a specific section of a subway line has officially begun operation or been opened for public use.
-
E.
subwayOperation
Indicates the operation or running of a subway system, relating transit services to the times, routes, or conditions under which subway trains are in service.
- F. None of above. chosen
Provenance (4 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61472cc081909e51b4a35a20ef43 |
completed | April 1, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:52 p.m.