Triple
T22708470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greatest Story Ever Told |
E561524
|
entity |
| Predicate | typicalUseInConcert |
P149403
|
FINISHED |
| Object | part of medleys |
—
|
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: part of medleys | Statement: [Greatest Story Ever Told, typicalUseInConcert, part of medleys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseInConcert Context triple: [Greatest Story Ever Told, typicalUseInConcert, part of medleys]
-
A.
typicalConcertProps
Indicates that the associated items are commonly used or present as standard properties or elements in a concert setting.
-
B.
typicalPerformanceOccasion
Indicates the usual or characteristic type of occasion, event, or context in which a performance typically takes place.
-
C.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
-
D.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
E.
usesInstrumentsOnStage
Indicates that an entity performs on stage while making use of musical instruments.
- F. None of above. chosen
Provenance (4 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178d11d4081909981872698b6c45e |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:17 p.m.