Triple
T116812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASME Boiler and Pressure Vessel Code |
E2355
|
entity |
| Predicate | sectionIVName |
P627
|
FINISHED |
| Object | Heating 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: Heating Boilers | Statement: [ASME Boiler and Pressure Vessel Code, sectionIVName, Heating Boilers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionIVName Context triple: [ASME Boiler and Pressure Vessel Code, sectionIVName, Heating Boilers]
-
A.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
section7Provides
Indicates that Section 7 serves as the source or provider of something (such as rights, obligations, benefits, or content) to another party or element.
-
C.
hasSectionKnownAs
chosen
Indicates that an entity includes a section or part that is referred to by a specific name.
-
D.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
E.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a256456d908190b52c937fe6c4343f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.