Triple
T919085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leadership in Energy and Environmental Design |
E19840
|
entity |
| Predicate | usesRatingScale |
P16725
|
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: [Leadership in Energy and Environmental Design, usesRatingScale, Certified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRatingScale Context triple: [Leadership in Energy and Environmental Design, usesRatingScale, Certified]
-
A.
rating
Indicates an evaluation relationship where one entity assigns a qualitative or quantitative score or judgment to another entity.
-
B.
scoreScale
chosen
Indicates the scale or range on which a score or rating is expressed or measured.
-
C.
ratingSystem
Indicates a system or method used to assign evaluative scores or rankings to items, actions, or entities based on defined criteria.
-
D.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
E.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2944ff88190a260be5355132ba5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.