Triple
T25035264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MF Horn |
E626958
|
entity |
| Predicate | creditedEnsembleType |
P31694
|
FINISHED |
| Object | big band |
—
|
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: big band | Statement: [MF Horn, creditedEnsembleType, big band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditedEnsembleType Context triple: [MF Horn, creditedEnsembleType, big band]
-
A.
hasEnsembleCast
chosen
Indicates that a work features an ensemble cast, meaning multiple principal performers share roughly equal prominence rather than having a single clear lead.
-
B.
associatedEnsembleOf
Indicates that one entity is linked or connected to a particular ensemble, typically as a member, contributor, or related component of that group.
-
C.
creditedIn
Indicates that an entity is acknowledged or listed as a contributor or source within a particular work, record, or context.
-
D.
creditsAre
Indicates that certain credits are assigned, attributed, or owed to a particular entity or set of entities.
-
E.
partOfCastEnsembleWith
Indicates that two or more performers are members of the same cast ensemble in a shared production.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4530598248190958310c3a3da1885 |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:08 a.m.