Triple
T23700817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphonies by Gustav Mahler |
E585589
|
entity |
| Predicate | usesOrchestraType |
P5560
|
FINISHED |
| Object | large 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: large symphony orchestra | Statement: [Symphonies by Gustav Mahler, usesOrchestraType, large symphony orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOrchestraType Context triple: [Symphonies by Gustav Mahler, usesOrchestraType, large symphony orchestra]
-
A.
hasOrchestraType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
B.
usesOrchestrationSimilarTo
Indicates that one entity employs an orchestration approach or mechanism that is similar to that used by another entity.
-
C.
hasOrchestration
Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
-
D.
hasSymphonyOrchestra
Indicates that an entity possesses, hosts, or is associated with a symphony orchestra.
-
E.
isOrchestral
Indicates that something involves, is written for, or is performed by an orchestra.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b682df6881908fe71be9833d3a88 |
completed | April 29, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.