Triple
T4906014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEED for Commercial Interiors |
E109913
|
entity |
| Predicate | certificationLevelsInclude |
P59356
|
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 Commercial Interiors, certificationLevelsInclude, Certified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certificationLevelsInclude Context triple: [LEED for Commercial Interiors, certificationLevelsInclude, Certified]
-
A.
certificationScope
Indicates the specific range, domain, or subject matter that a given certification covers or applies to.
-
B.
hasCertificationStandard
Indicates that an entity complies with, or is associated with, a specific certification standard.
-
C.
certificationBy
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
-
D.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
E.
requiresCertification
Indicates that one entity can only be performed, accessed, or considered valid if another entity has an appropriate certification.
- 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.