Triple
T3772487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGM suburban rail line |
E83228
|
entity |
| Predicate | hasRouteCharacteristic |
P37949
|
FINISHED |
| Object | coastal alignment |
—
|
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: coastal alignment | Statement: [TGM suburban rail line, hasRouteCharacteristic, coastal alignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteCharacteristic Context triple: [TGM suburban rail line, hasRouteCharacteristic, coastal alignment]
-
A.
hasRouteFeature
chosen
Indicates that a route possesses or is associated with a specific characteristic, attribute, or feature.
-
B.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
C.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
D.
hasNavigationCharacteristic
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
-
E.
hasRouteIdentifier
Indicates that an entity is associated with a specific route code or identifier used to distinguish it from other routes.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc3219b881908a2f82126f9a679d |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.