Triple
T29284077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romeo + Juliet (ballet) |
E742460
|
entity |
| Predicate | usesScore |
P181235
|
FINISHED |
| Object | Romeo and Juliet (Prokofiev) |
—
|
NE NERFINISHED |
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: Romeo and Juliet (Prokofiev) | Statement: [Romeo + Juliet (ballet), usesScore, Romeo and Juliet (Prokofiev)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScore Context triple: [Romeo + Juliet (ballet), usesScore, Romeo and Juliet (Prokofiev)]
-
A.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
B.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
C.
usesCompositeScore
Indicates that an entity bases its evaluation, decision, or outcome on a combined score derived from multiple underlying metrics or factors.
-
D.
usesExistingScore
Indicates that an entity relies on or applies a previously calculated or established score rather than generating a new one.
-
E.
usesRankingPoints
Indicates that one entity bases its ordering, evaluation, or decision-making on ranking points associated with another entity.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 28, 2026, 12:56 p.m.