Triple
T19962464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEED Platinum |
E479848
|
entity |
| Predicate | requiresMinimumPoints |
P22279
|
FINISHED |
| Object | 80 points under LEED v4 BD+C |
—
|
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: 80 points under LEED v4 BD+C | Statement: [LEED Platinum, requiresMinimumPoints, 80 points under LEED v4 BD+C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresMinimumPoints Context triple: [LEED Platinum, requiresMinimumPoints, 80 points under LEED v4 BD+C]
-
A.
requiresMinimumScore
chosen
Indicates that one entity can only be obtained, accessed, or considered valid if another entity’s score meets or exceeds a specified minimum threshold.
-
B.
requiredPledgeFrom
Indicates that one entity mandates or demands a pledge or commitment from another entity as a prerequisite or condition.
-
C.
requiresMinimumCapital
Indicates that one entity can only proceed, be valid, or be permitted if a specified minimum amount of capital is available or provided.
-
D.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
E.
minimumDistanceRequirement
Indicates that there is a required minimum distance that must be maintained between the related entities.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af51b4c81909ba156a489cbc551 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.