Triple
T8785450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odds Against Tomorrow |
E209032
|
entity |
| Predicate | hasScoreStyle |
P73604
|
FINISHED |
| Object | jazz 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: jazz score | Statement: [Odds Against Tomorrow, hasScoreStyle, jazz score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreStyle Context triple: [Odds Against Tomorrow, hasScoreStyle, jazz score]
-
A.
hasOriginalScoreStyle
chosen
Indicates that an entity’s original score is composed or arranged in a particular musical style or genre.
-
B.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
-
C.
hasScoreRecord
Indicates that an entity is associated with a specific score entry or scoring record.
-
D.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
E.
hasScoreboard
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f758d348190804942d985f2337c |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.