Triple
T10395859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite from 'Exodus: Gods and Kings' |
E245013
|
entity |
| Predicate | intendedForEnsemble |
P17036
|
FINISHED |
| Object | symphony orchestra |
—
|
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: symphony orchestra | Statement: [Suite from 'Exodus: Gods and Kings', intendedForEnsemble, symphony orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedForEnsemble Context triple: [Suite from 'Exodus: Gods and Kings', intendedForEnsemble, symphony orchestra]
-
A.
intendedEnsemble
chosen
Indicates that one entity is designed, chosen, or specified to function as the ensemble or group counterpart associated with another entity.
-
B.
isPartOfEnsemble
Indicates that an entity belongs to, or is a member of, a larger group or ensemble.
-
C.
usesMusicEnsemble
Indicates that one entity employs or incorporates a particular music ensemble in carrying out an action, function, or production.
-
D.
typeOfEnsemble
Indicates the specific kind or category of ensemble that an entity belongs to or represents.
-
E.
hasMusicalEnsembleType
Indicates that an entity is associated with or classified as a particular type of musical ensemble.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9cf79348190975d6c1791e3b621 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:06 p.m.