Triple
T4905965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEED for Existing Buildings |
E109912
|
entity |
| Predicate | hasCertificationLevels |
P59355
|
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 Existing Buildings, hasCertificationLevels, Certified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCertificationLevels Context triple: [LEED for Existing Buildings, hasCertificationLevels, Certified]
-
A.
hasCertificationStandard
Indicates that an entity complies with, or is associated with, a specific certification standard.
-
B.
hasCertificationLabel
Indicates that an entity bears or is associated with a specific certification label signifying compliance with defined standards or criteria.
-
C.
hasRankLevels
Indicates that an entity is associated with one or more hierarchical rank levels within a ranking or grading system.
-
D.
recognizesLevel
Indicates that one entity acknowledges, identifies, or is aware of the degree, rank, or intensity associated with another entity.
-
E.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e72ed5c819081104c99a398e0af |
completed | March 20, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6cc228088190849f23b7bd4cf549 |
completed | March 20, 2026, 3:50 p.m. |
Created at: March 20, 2026, 1:29 p.m.