Triple
T26905447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExpressTram |
E677238
|
entity |
| Predicate | hasGuidewayType |
P9536
|
FINISHED |
| Object | elevated guideway |
—
|
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: elevated guideway | Statement: [ExpressTram, hasGuidewayType, elevated guideway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuidewayType Context triple: [ExpressTram, hasGuidewayType, elevated guideway]
-
A.
guidewayType
chosen
Indicates the specific kind or classification of guideway used in a transportation or movement system.
-
B.
isFixedGuideway
Indicates that the movement or operation of an entity is constrained to a predetermined, dedicated path or track, rather than operating freely.
-
C.
hasGreenwaySegment
Indicates that an entity includes, is connected to, or is composed of one or more segments of a greenway path or corridor.
-
D.
hasGatewayType
Indicates that an entity is associated with or configured to use a specific type or category of gateway.
-
E.
hasCarriagewayType
Indicates the specific structural or functional type of carriageway associated with a road segment (e.g., single, dual, or other carriageway configurations).
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 5:58 a.m.