Triple
T30611047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BREEAM Outstanding |
E779178
|
entity |
| Predicate | assessedAcross |
P2335
|
FINISHED |
| Object | management |
—
|
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: management | Statement: [BREEAM Outstanding, assessedAcross, management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assessedAcross Context triple: [BREEAM Outstanding, assessedAcross, management]
-
A.
assessedBy
Indicates that an entity has been evaluated, examined, or judged by another entity (typically an agent or authority).
-
B.
assessmentBasis
Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
-
C.
assessment
Indicates an evaluation or judgment made about an entity’s quality, performance, or characteristics.
-
D.
across
Indicates a spatial relationship where one entity is on the opposite side of, or extending from one side to the other side of, another entity or area.
-
E.
appliesAcross
chosen
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689e773ac81908b79eef4d4aae5cb |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.