Triple
T28331185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Études Op. 10 |
E717542
|
entity |
| Predicate | keyCatalogueNumber |
P164282
|
FINISHED |
| Object | Op. 10 |
—
|
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: Op. 10 | Statement: [Études Op. 10, keyCatalogueNumber, Op. 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCatalogueNumber Context triple: [Études Op. 10, keyCatalogueNumber, Op. 10]
-
A.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
B.
keyOfPart
Indicates that one entity functions as the key or identifier used to reference, access, or distinguish a specific part of another entity.
-
C.
keyExample
Indicates that something serves as a representative or illustrative instance of a key concept, feature, or case.
-
D.
keyPosition
Indicates the specific location or placement of a key within a defined space or system.
-
E.
keyCustom
Indicates that something has a user-defined or non-standard key used for identification, access, or configuration.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64bce044c81908c397f6eb05e74c1 |
completed | May 2, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 28, 2026, 12:32 a.m.