Triple
T29742666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean, Count of Paris |
E752653
|
entity |
| Predicate | throneStatus |
P167834
|
FINISHED |
| Object | pretender to a defunct throne |
—
|
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: pretender to a defunct throne | Statement: [Jean, Count of Paris, throneStatus, pretender to a defunct throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: throneStatus Context triple: [Jean, Count of Paris, throneStatus, pretender to a defunct throne]
-
A.
tookThroneFollowing
Indicates that one entity assumed or claimed a throne or rulership position directly after another entity, in a succession context.
-
B.
monarchSheIsHeirTo
Indicates that the subject is the designated heir to the specified monarch’s throne or title.
-
C.
succeedsOnThroneOf
Indicates that one entity becomes the next ruler occupying the throne previously held by another entity.
-
D.
throneName
Indicates the official royal or regnal name adopted by a ruler when they ascend to the throne.
-
E.
throneNameStatus
Indicates the status or condition of an entity’s throne-related name or title, such as whether it is current, former, valid, or otherwise classified.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673645c888190bdffeb6448487ec4 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 7:49 p.m.