Triple
T32574896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Volodymyr |
E832616
|
entity |
| Predicate | successorTitleInSomePeriods |
P8415
|
FINISHED |
| Object | Prince of Volhynia |
—
|
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: Prince of Volhynia | Statement: [Prince of Volodymyr, successorTitleInSomePeriods, Prince of Volhynia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTitleInSomePeriods Context triple: [Prince of Volodymyr, successorTitleInSomePeriods, Prince of Volhynia]
-
A.
successorTitleForHolders
Indicates that one title is the official successor title that replaces or follows the titles previously held by certain holders.
-
B.
successorTitlesComparedWith
Indicates that the titles of successor entities are being compared to determine their relative similarity, difference, or ordering.
-
C.
successorTitleContext
Indicates the contextual circumstances or framework under which one title succeeds another.
-
D.
successorTitle
chosen
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
E.
successorTitlePossible
Indicates that a particular title is eligible or allowed to be used as the successor to another title.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 1, 2026, 1:04 a.m.