Triple
T16303709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coco (Broadway musical) |
E395852
|
entity |
| Predicate | hasScore |
P15617
|
FINISHED |
| Object | André Previn score |
—
|
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: André Previn score | Statement: [Coco (Broadway musical), hasScore, André Previn score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScore Context triple: [Coco (Broadway musical), hasScore, André Previn score]
-
A.
hasScoreRecord
Indicates that an entity is associated with a specific score entry or scoring record.
-
B.
hasScoreCharacteristic
Indicates that one entity possesses or is associated with a particular scoring-related characteristic or property.
-
C.
isScoreFor
chosen
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
D.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
-
E.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e35157481909e5604b7dae7a2a2 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.