Triple
T36123187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Superior City wreck |
E1044799
|
entity |
| Predicate | originalPropulsionType |
P20991
|
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: [SS Superior City wreck, originalPropulsionType, steam-powered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPropulsionType Context triple: [SS Superior City wreck, originalPropulsionType, steam-powered]
-
A.
originalPropulsion
chosen
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
B.
propulsionTypeCode
Indicates the specific method or system by which an object or vehicle is propelled or driven.
-
C.
plannedPropulsionType
Indicates the type of propulsion system that is intended or scheduled to be used for an object or vehicle.
-
D.
propulsionTypeVariant
Indicates a relationship where one propulsion type is a specific variant or subtype of another propulsion type.
-
E.
propulsionTypeOfSystem
Indicates the type of propulsion mechanism that a system uses to generate thrust or movement.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.