Triple
T903751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisbon Tramway |
E19501
|
entity |
| Predicate | hasPropulsionSystem |
P14429
|
FINISHED |
| Object | electric traction |
—
|
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: electric traction | Statement: [Lisbon Tramway, hasPropulsionSystem, electric traction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropulsionSystem Context triple: [Lisbon Tramway, hasPropulsionSystem, electric traction]
-
A.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
B.
propulsionCycle
Indicates the type or pattern of propulsion operation or cycle that characterizes how a system generates and sustains thrust or movement.
-
C.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
D.
hasMotivePowerType
chosen
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
E.
hasLocomotive
Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad58334881908df191140b786780 |
completed | March 1, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69a4aa98caec8190bbcc38320090f058 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.