Triple
T31394721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 5 |
E800833
|
entity |
| Predicate | hasKeyRange |
P139604
|
FINISHED |
| Object | various keys depending on composer |
—
|
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: various keys depending on composer | Statement: [Symphony No. 5, hasKeyRange, various keys depending on composer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyRange Context triple: [Symphony No. 5, hasKeyRange, various keys depending on composer]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasKeyboardRange
chosen
Indicates that one entity possesses or supports a specified span of keys or notes across a keyboard-based input or instrument.
-
C.
hasKeySpace
Indicates that one entity defines, owns, or is associated with the namespace or set of valid keys used to identify or access elements in another entity.
-
D.
hasBlockRangeStart
Indicates the starting position or index of a contiguous block or range associated with an entity.
-
E.
hasKeyApprox
Indicates that one entity possesses a key that approximately matches, corresponds to, or can operate with another entity, but not necessarily with exact or perfect equivalence.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 9:19 p.m.