Triple
T32362404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymonda, Op. 57 |
E826898
|
entity |
| Predicate | firstJeanDeBrienneInterpreter |
P206256
|
FINISHED |
| Object | Pavel Gerdt |
E802253
|
NE 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: Pavel Gerdt | Statement: [Raymonda, Op. 57, firstJeanDeBrienneInterpreter, Pavel Gerdt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstJeanDeBrienneInterpreter Context triple: [Raymonda, Op. 57, firstJeanDeBrienneInterpreter, Pavel Gerdt]
-
A.
firstHolderAsDauphin
Indicates that the subject is the first person to have held a particular title or position in the capacity of Dauphin (heir apparent).
-
B.
predecessorInBurgundy
Indicates that one entity previously held a position, role, or status in Burgundy that was later held by the other entity.
-
C.
firstBishop
Indicates that one entity is the first bishop (earliest in time or rank) associated with or holding episcopal authority over another entity.
-
D.
FrenchCommander
Indicates that an entity serves as a military commander associated with France.
-
E.
Jean II d’Estrées-rank
Indicates the military or noble rank held by Jean II d’Estrées.
- F. None of above. chosen
Provenance (5 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a33e8aa42448190ac5353dd6c57ac47 |
completed | June 18, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:49 a.m.