Triple
T24763166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASL |
E619506
|
entity |
| Predicate | relatedStationCodeType |
P65507
|
FINISHED |
| Object | station code |
—
|
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: station code | Statement: [ASL, relatedStationCodeType, station code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedStationCodeType Context triple: [ASL, relatedStationCodeType, station code]
-
A.
relatedStationNumber
Indicates that there is an associated or corresponding station identified by a particular station number.
-
B.
associatedStation
chosen
Indicates a relationship where one entity is linked or connected to a particular station as its relevant or related station.
-
C.
associatedStationQualifier
Indicates that a station is linked to another station with a specific qualifying role or context (such as type, function, or relationship).
-
D.
associatedStationCategory
Indicates that one entity is linked to, or classified under, a particular category of station.
-
E.
associatedWithStationName
Indicates a relationship where something is linked or connected to a particular station identified by its name.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4:28 a.m.