Triple
T36735856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dance of Life: Tallinn Mass |
E907470
|
entity |
| Predicate | placeInspiredBy |
P14480
|
FINISHED |
| Object | Tallinn |
—
|
NE NERFINISHED |
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: Tallinn | Statement: [Dance of Life: Tallinn Mass, placeInspiredBy, Tallinn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInspiredBy Context triple: [Dance of Life: Tallinn Mass, placeInspiredBy, Tallinn]
-
A.
inspiredByPlace
chosen
Indicates that something (such as a work, idea, or creation) originates from or is significantly influenced by a particular location or environment.
-
B.
locationGaveRiseTo
Indicates that a particular location is the origin or source from which something (such as an event, movement, phenomenon, or entity) emerged or developed.
-
C.
inspiredByOrRelatedTo
Indicates that one entity draws inspiration from, is influenced by, or is otherwise thematically or conceptually connected to another entity.
-
D.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
E.
hasPlaceNamesakeIn
Indicates that something is named after a particular place 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:12 p.m.