Triple
T11195639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Poland |
E264913
|
entity |
| Predicate | typeOfSuccessionTitle |
P6489
|
FINISHED |
| Object | hereditary title |
—
|
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: hereditary title | Statement: [Prince of Poland, typeOfSuccessionTitle, hereditary title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSuccessionTitle Context triple: [Prince of Poland, typeOfSuccessionTitle, hereditary title]
-
A.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
B.
successorTitleContext
Indicates the contextual circumstances or framework under which one title succeeds another.
-
C.
titleType
chosen
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
D.
titleReign
Indicates the period during which a particular title was officially held or exercised by an entity.
-
E.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8bf14e481908563b15790af4d20 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.