Triple
T30024905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 2 |
E762852
|
entity |
| Predicate | composedInExile |
P73291
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Symphony No. 2, composedInExile, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composedInExile Context triple: [Symphony No. 2, composedInExile, true]
-
A.
writtenInExile
chosen
Indicates that a work was created while its author was living away from their homeland, typically due to expulsion, banishment, or forced displacement.
-
B.
formedInExile
Indicates that an entity (such as a group, organization, or movement) was created while its founders or core members were living away from their homeland, typically due to displacement, banishment, or political exile.
-
C.
continuedInExile
Indicates that an entity remained in a state of exile for a further period of time beyond an initial point or event.
-
D.
exiledWith
Indicates that two or more entities were banished or forced to leave a place together as part of the same exile.
-
E.
livedInExileIn
Indicates that an entity spent a period of time living outside its home country or usual place of residence due to exile, in a specified 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 6:48 p.m.