Triple
T15333109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockwell |
E366589
|
entity |
| Predicate | hasRealTimeArrivalDisplays |
P30947
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rockwell, hasRealTimeArrivalDisplays, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealTimeArrivalDisplays Context triple: [Rockwell, hasRealTimeArrivalDisplays, yes]
-
A.
hasDepartureScreens
Indicates that a location or facility is equipped with screens displaying departure information for services such as trains, buses, or flights.
-
B.
usedOnDepartureBoards
Indicates that something (such as a name, code, or label) is the form that is shown on departure boards to represent a service or destination.
-
C.
hasRealTimeInformation
chosen
Indicates that up-to-date, continuously refreshed information is available about the related entity or event.
-
D.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
E.
cityTerminalStatus
Indicates the operational or functional status of a city’s terminal (such as an airport, bus, or train terminal) within a given context or system.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e0268608190947a58f559a67717 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.