Triple
T4044072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monument Metro station |
E84020
|
entity |
| Predicate | hasNextTrainIndicators |
P53774
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Monument Metro station, hasNextTrainIndicators, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNextTrainIndicators Context triple: [Monument Metro station, hasNextTrainIndicators, true]
-
A.
hasTramDestination
Indicates that a tram route or service goes to or terminates at a specified destination.
-
B.
hasStopNear
Indicates that one entity has a stop or stopping point located in close proximity to another entity.
-
C.
hasAdjacentStationOnIND
Indicates that one station is directly next to another station on the IND (Independent Subway System) line, with no other stations in between.
-
D.
railStatus
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
-
E.
railLineStatusAfterward
Indicates the condition or operational status of a rail line after a specified event or time period has occurred.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb5d759c8190b61fbbe94ffe2bf7 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.