Triple
T9408990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Light Train |
E226658
|
entity |
| Predicate | hasServiceRange |
P76953
|
FINISHED |
| Object | short-distance urban trips |
—
|
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: short-distance urban trips | Statement: [Light Train, hasServiceRange, short-distance urban trips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceRange Context triple: [Light Train, hasServiceRange, short-distance urban trips]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasFacilityRange
chosen
Indicates that an entity provides or is associated with a facility that covers a specified range (such as capacity, distance, or operational extent).
-
C.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
D.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
E.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd52547f0c81908ed4f53b9f05ebaa |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.