Triple
T16563379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsche Bank Building |
E402394
|
entity |
| Predicate | contaminatedBy |
P24582
|
FINISHED |
| Object | asbestos |
—
|
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: asbestos | Statement: [Deutsche Bank Building, contaminatedBy, asbestos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contaminatedBy Context triple: [Deutsche Bank Building, contaminatedBy, asbestos]
-
A.
containsContaminant
chosen
Indicates that one entity includes, holds, or is tainted by an unwanted or harmful contaminating substance or element.
-
B.
infiltratedBy
Indicates that an entity has been secretly entered, penetrated, or taken over by another entity, typically in a covert or unauthorized manner.
-
C.
wasHeavilyPollutedDuring
Indicates that a place or environment experienced a high level of pollution during a specified time period.
-
D.
impregnatedBy
Indicates that one entity has caused another entity to become pregnant.
-
E.
historicallyPollutedBy
Indicates that an entity has experienced pollution in the past as a result of actions or emissions from another entity.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576f757881909bfc6611361ed16d |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.