Triple
T4691505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elevador de Santa Justa |
E104043
|
entity |
| Predicate | originalTractionType |
P19787
|
FINISHED |
| Object | steam-powered |
—
|
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: steam-powered | Statement: [Elevador de Santa Justa, originalTractionType, steam-powered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTractionType Context triple: [Elevador de Santa Justa, originalTractionType, steam-powered]
-
A.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
-
B.
primaryTraction
Indicates that one entity serves as the main source or means of traction, pulling power, or driving force for another entity or process.
-
C.
successorTractionType
Indicates that one traction type directly follows or replaces another in a sequence or evolution of traction systems.
-
D.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
E.
tractionType
chosen
Indicates the type or method of traction applied or used in relation to an entity or system.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.