Triple
T17612674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGC |
E429000
|
entity |
| Predicate | appliesToStationCategory |
P8936
|
FINISHED |
| Object | A1 category station |
—
|
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: A1 category station | Statement: [AGC, appliesToStationCategory, A1 category station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToStationCategory Context triple: [AGC, appliesToStationCategory, A1 category station]
-
A.
associatedStationCategory
chosen
Indicates that one entity is linked to, or classified under, a particular category of station.
-
B.
appliesToTransitStation
Indicates that something (such as a rule, feature, condition, or attribute) is specifically relevant or applicable to a transit station.
-
C.
hasStationTypeAt
Indicates that a specific type of station is present or assigned at a particular location or point.
-
D.
appliesToTransportFacilityType
Indicates that something is relevant or applicable specifically to a particular type or category of transport facility.
-
E.
isOneOfStationsServing
Indicates that an entity is among the set of stations that provide service to or are responsible for another specified entity.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2eaa348190a8226eef8c0d6e31 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.