Triple
T6397717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Structures I |
E143980
|
entity |
| Predicate | catalogueNote |
P70400
|
FINISHED |
| Object | early major work of Pierre Boulez |
—
|
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: early major work of Pierre Boulez | Statement: [Structures I, catalogueNote, early major work of Pierre Boulez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueNote Context triple: [Structures I, catalogueNote, early major work of Pierre Boulez]
-
A.
catalogueEntry
Indicates that an item is recorded as an entry within a catalogue or organized listing.
-
B.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
C.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
D.
cataloguePrefix
Indicates that one entity serves as the initial or leading segment of another entity’s catalogue identifier or listing code.
-
E.
catalogueRaisonneNumber
Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06896d180819091548a728e903184 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:35 p.m.