Triple
T23345202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flexity Zürich tram |
E591836
|
entity |
| Predicate | hasArticulatedSections |
P133309
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Flexity Zürich tram, hasArticulatedSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArticulatedSections Context triple: [Flexity Zürich tram, hasArticulatedSections, yes]
-
A.
articulatedSections
chosen
Indicates that one entity is composed of multiple connected parts or segments that can move relative to each other.
-
B.
isMultiSectional
Indicates that something is composed of or divided into multiple distinct sections or parts.
-
C.
hasArticulation
Indicates that one entity possesses or exhibits a specific type or structure of articulation in relation to another entity or system.
-
D.
hasSurfaceSections
Indicates that an entity is composed of or divided into distinct sections or parts of its surface.
-
E.
hasVerticalSection
Indicates that one entity possesses or includes a distinct vertical section or segment as part of its structure or representation.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1983697408190b31817174ed4e77b |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.