Triple
T24972132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Petit Dauphin |
E624918
|
entity |
| Predicate | appliesToSuccessionStatus |
P16392
|
FINISHED |
| Object | heir apparent |
—
|
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: heir apparent | Statement: [Le Petit Dauphin, appliesToSuccessionStatus, heir apparent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToSuccessionStatus Context triple: [Le Petit Dauphin, appliesToSuccessionStatus, heir apparent]
-
A.
hasRoleInSuccession
Indicates that an entity holds a specific role or position within a defined line or order of succession.
-
B.
successionLawStatus
chosen
Indicates the legal status or condition governing how succession or inheritance is determined or applied.
-
C.
hasSuccession
Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
-
D.
supportedSuccessionOf
Indicates that one entity actively endorsed or helped bring about the transfer of power, position, or role from a predecessor to a successor.
-
E.
hasModeOfSuccession
Indicates the rule or method by which authority, title, or position is passed from one holder to the next.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:01 a.m.