Triple
T37476849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-23 |
E931303
|
entity |
| Predicate | isTerminalStationCode |
P187808
|
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: [A-23, isTerminalStationCode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTerminalStationCode Context triple: [A-23, isTerminalStationCode, true]
-
A.
isPassengerStationCode
Indicates that a given code is officially assigned to identify a particular passenger station.
-
B.
isTerminalForSomeTrains
Indicates that a station or stop serves as the final destination (terminus) for at least one train route.
-
C.
formerTerminalStation
Indicates that a location once served as the end point (terminus) of a transportation line or route but no longer holds that status.
-
D.
isKeyIntercityTerminalFor
Indicates that a location serves as a primary intercity transportation hub or terminal for a specified area, route, or network.
-
E.
isRailwayStation
Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or freight.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e6631588190a1a9ce9289f4ccb0 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb8dfe70d08190b2558cdfcc1b15c0 |
completed | May 6, 2026, 6:52 p.m. |
Created at: May 3, 2026, 4:17 p.m.