Triple
T10088359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 7 "Sinfonia antartica" |
E215277
|
entity |
| Predicate | hasInstrumentationGroup |
P62771
|
FINISHED |
| Object | strings |
—
|
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: strings | Statement: [Symphony No. 7 "Sinfonia antartica", hasInstrumentationGroup, strings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstrumentationGroup Context triple: [Symphony No. 7 "Sinfonia antartica", hasInstrumentationGroup, strings]
-
A.
hasTypeOfInstrumentation
chosen
Indicates that one entity uses, involves, or is characterized by a particular type of instrumentation.
-
B.
hasInstrumentRole
Indicates that an entity participates in an action or process specifically in the capacity of an instrument or means by which that action is carried out.
-
C.
hasStationGroup
Indicates that an entity is associated with, or belongs to, a particular group or collection of stations.
-
D.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
E.
hasTaskGroup
Indicates that an entity is associated with, or belongs to, a specific task group that organizes or groups related tasks.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04875748190a81d1e9ad68dda96 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.