Triple
T21871766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live in Stuttgart 1989 |
E540018
|
entity |
| Predicate | featuresMaterialAssociatedWith |
P59790
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Live in Stuttgart 1989, featuresMaterialAssociatedWith, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMaterialAssociatedWith Context triple: [Live in Stuttgart 1989, featuresMaterialAssociatedWith, Yes]
-
A.
featuresMaterialType
Indicates that an entity is characterized by or incorporates a specific type of material.
-
B.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
associatedWithMaterial
chosen
Indicates a relationship where something is linked or connected to a particular material, typically as its substance, component, or relevant physical medium.
-
E.
materialDepicted
Indicates that a work or representation visually portrays or includes a particular material as part of its subject.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f3368d488190a37224b587858ab0 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:58 p.m.