Triple
T24004918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B&O No. 25 William Mason |
E594344
|
entity |
| Predicate | hasBoiler |
P47501
|
FINISHED |
| Object | 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: fire-tube boiler | Statement: [B&O No. 25 William Mason, hasBoiler, fire-tube boiler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoiler Context triple: [B&O No. 25 William Mason, hasBoiler, fire-tube boiler]
-
A.
hasBoilerPosition
Indicates the spatial placement or designated location of a boiler relative to another object or within a given environment.
-
B.
boilerType
chosen
Indicates the specific kind or category of boiler associated with an entity, such as its design, fuel source, or operating characteristics.
-
C.
hasBoilerPressure
Indicates that an entity possesses or is associated with a specific boiler pressure value.
-
D.
hasBoilingCenter
Indicates that something possesses or contains a central region or core area where boiling occurs.
-
E.
boilers
Indicates that an entity functions as or is equipped with boilers, typically for heating or generating steam.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d4681fd88190949c5c91d4f94910 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.