Triple
T3131115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Warrior (1860) |
E65414
|
entity |
| Predicate | boilers |
P45551
|
FINISHED |
| Object | 10 rectangular boilers |
—
|
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: 10 rectangular boilers | Statement: [HMS Warrior (1860), boilers, 10 rectangular boilers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boilers Context triple: [HMS Warrior (1860), boilers, 10 rectangular boilers]
-
A.
bore
Indicates that one entity caused another entity to feel uninterested, tired, or lacking in engagement.
-
B.
furnaceType
Indicates the specific kind or category of furnace associated with an entity.
-
C.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
D.
hasHeating
Indicates that an entity is equipped with or provides a heating system or heating capability.
-
E.
coolant
Indicates that one entity functions as a coolant for another, serving to absorb and remove heat from it.
- F. None of above. chosen
Provenance (4 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada54b0e688190b691771f17f4c721 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.