Triple
T30024906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 2 |
E762852
|
entity |
| Predicate | composerResidenceDuringComposition |
P3044
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Symphony No. 2, composerResidenceDuringComposition, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerResidenceDuringComposition Context triple: [Symphony No. 2, composerResidenceDuringComposition, United States]
-
A.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
-
B.
artistResidenceAtTimeOfWork
chosen
Indicates the place where an artist was living at the time a particular work was created.
-
C.
hasComposerResidence
Indicates that a composer has a particular place as their residence or primary dwelling.
-
D.
artistResidence
Indicates that a given location is the place where an artist lives or is based.
-
E.
workLocationOfComposer
Indicates that a specified location is the place where a particular composer works or carries out their professional musical activities.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 6:48 p.m.