Triple
T4845001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEED for New Construction |
E108266
|
entity |
| Predicate | usesCertificationLevels |
P58110
|
FINISHED |
| Object | Certified |
—
|
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: Certified | Statement: [LEED for New Construction, usesCertificationLevels, Certified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCertificationLevels Context triple: [LEED for New Construction, usesCertificationLevels, Certified]
-
A.
requiresCertification
Indicates that one entity can only be performed, accessed, or considered valid if another entity has an appropriate certification.
-
B.
hasCertificationStandard
Indicates that an entity complies with, or is associated with, a specific certification standard.
-
C.
hasCertificationLabel
chosen
Indicates that an entity bears or is associated with a specific certification label signifying compliance with defined standards or criteria.
-
D.
certificationUS
Indicates that an entity holds or is associated with a certification that is recognized, issued, or valid within the United States.
-
E.
certificationScope
Indicates the specific range, domain, or subject matter that a given certification covers or applies to.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.