Triple
T37665155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purpur Block |
E937803
|
entity |
| Predicate | foundInStructureMaterialSet |
P104293
|
FINISHED |
| Object | End City towers |
—
|
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: End City towers | Statement: [Purpur Block, foundInStructureMaterialSet, End City towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInStructureMaterialSet Context triple: [Purpur Block, foundInStructureMaterialSet, End City towers]
-
A.
foundInStructure
Indicates that an entity is located within, contained by, or structurally part of another entity or structure.
-
B.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
C.
featuresMaterialType
chosen
Indicates that an entity is characterized by or incorporates a specific type of material.
-
D.
isMaterialSpecific
Indicates that a relationship, rule, or property applies only to a particular material or set of materials, rather than being generally applicable.
-
E.
materialFound
Indicates that a particular material is present, discovered, or detected in association with a specified entity or location.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: May 3, 2026, 4:18 p.m.