Triple
T26067256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Energy Conservation Code |
E657435
|
entity |
| Predicate | editionExample |
P160326
|
FINISHED |
| Object | 2018 IECC |
—
|
NE NERFINISHED |
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: 2018 IECC | Statement: [International Energy Conservation Code, editionExample, 2018 IECC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editionExample Context triple: [International Energy Conservation Code, editionExample, 2018 IECC]
-
A.
editionExample
chosen
Indicates that one entity is an example or specific instance of a particular edition of another entity.
-
B.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
C.
editionPattern
Indicates a recurring structure or template that characterizes how different editions or versions of something are organized or produced.
-
D.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
E.
editionSize
Indicates the total number of copies or instances produced in a particular edition of something.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 7:25 p.m.