Triple
T35094228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus 8 |
E1012819
|
entity |
| Predicate | catalogueDesignationFor |
P182517
|
FINISHED |
| Object | Violanta |
—
|
NE NERFINISHED |
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: Violanta | Statement: [Opus 8, catalogueDesignationFor, Violanta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueDesignationFor Context triple: [Opus 8, catalogueDesignationFor, Violanta]
-
A.
collectionDesignation
Indicates that one entity assigns or specifies a particular collection label or designation for another entity.
-
B.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
C.
bdDesignation
Indicates that one entity is formally assigned or designated as having a particular role, status, or classification in relation to another entity.
-
D.
designatorCategory
Indicates the classification or type assigned to a designator within a given system or context.
-
E.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.