Triple
T27696925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Pacific AC-8 |
E698321
|
entity |
| Predicate | fireboxType |
P7338
|
FINISHED |
| Object | conventional fire-tube boiler |
—
|
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: conventional fire-tube boiler | Statement: [Southern Pacific AC-8, fireboxType, conventional fire-tube boiler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireboxType Context triple: [Southern Pacific AC-8, fireboxType, conventional fire-tube boiler]
-
A.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
B.
furnaceType
chosen
Indicates the specific kind or category of furnace associated with an entity.
-
C.
fireTowerType
Indicates the specific classification or category of a fire tower in relation to that tower.
-
D.
boilerType
Indicates the specific kind or category of boiler associated with an entity, such as its design, fuel source, or operating characteristics.
-
E.
fireSupportType
Indicates the specific kind or category of supporting fire (such as artillery, air support, or naval gunfire) being provided in a military context.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359fecc081908e1794c1905c5cc4 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:54 p.m.