Triple
T20693456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europeras |
E508606
|
entity |
| Predicate | hasScoreType |
P141114
|
FINISHED |
| Object | graphic notation |
—
|
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: graphic notation | Statement: [Europeras, hasScoreType, graphic notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreType Context triple: [Europeras, hasScoreType, graphic notation]
-
A.
hasScoreboardType
Indicates the specific kind or category of scoreboard associated with an entity.
-
B.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
-
C.
hasScoreCharacteristic
Indicates that one entity possesses or is associated with a particular scoring-related characteristic or property.
-
D.
scoringType
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
E.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10fc4088190ab71ef078600954b |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:09 p.m.