Triple
T25112751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Brig Niagara |
E629042
|
entity |
| Predicate | hasSupplementaryPropulsion |
P21496
|
FINISHED |
| Object | diesel engine (modern) |
—
|
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: diesel engine (modern) | Statement: [U.S. Brig Niagara, hasSupplementaryPropulsion, diesel engine (modern)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupplementaryPropulsion Context triple: [U.S. Brig Niagara, hasSupplementaryPropulsion, diesel engine (modern)]
-
A.
hasPropulsionComponent
Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
-
B.
auxiliaryPropulsion
chosen
Indicates that an entity provides secondary or backup propulsion support to another entity or system.
-
C.
propulsionFeature
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
D.
propulsionMedium
Indicates the medium or substance through which propulsion is generated or transmitted for movement.
-
E.
hasPropeller
Indicates that an entity is equipped with or possesses a propeller as a functional component.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 6:27 a.m.