Triple
T20704713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Escape |
E508871
|
entity |
| Predicate | basedOnScoreStyle |
P73604
|
FINISHED |
| Object | avant-garde orchestral |
—
|
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: avant-garde orchestral | Statement: [No Escape, basedOnScoreStyle, avant-garde orchestral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnScoreStyle Context triple: [No Escape, basedOnScoreStyle, avant-garde orchestral]
-
A.
scoringType
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
B.
hasOriginalScoreStyle
chosen
Indicates that an entity’s original score is composed or arranged in a particular musical style or genre.
-
C.
decisiveScoreType
Indicates the type or category of score used to determine a decisive outcome in a comparison or decision process.
-
D.
cutScoresSetBy
Indicates that one party determines or establishes the cutoff scores used to evaluate or classify another entity.
-
E.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c18ea874819092a125d9f929a311 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:13 p.m.