Triple
T8684493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM-93 tram |
E206120
|
entity |
| Predicate | vehicleRole |
P7949
|
FINISHED |
| Object | passenger transport |
—
|
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: passenger transport | Statement: [LM-93 tram, vehicleRole, passenger transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRole Context triple: [LM-93 tram, vehicleRole, passenger transport]
-
A.
transportRole
chosen
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
B.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
D.
vehicleFamily
Indicates that two vehicles belong to the same family or category based on shared design, platform, or lineage.
-
E.
mobilityRole
Indicates the functional role or capacity an entity has in enabling, supporting, or performing movement or transportation.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aeae740819099093906ccc5f640 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.