Triple
T19466838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dauphiné |
E487021
|
entity |
| Predicate | rulerTitleMeaning |
P4542
|
FINISHED |
| Object | heir apparent to the French 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: heir apparent to the French throne | Statement: [Dauphiné, rulerTitleMeaning, heir apparent to the French throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulerTitleMeaning Context triple: [Dauphiné, rulerTitleMeaning, heir apparent to the French throne]
-
A.
titleMeaning
chosen
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
B.
traditionalRulerTitleInArea
Indicates that a specific traditional ruler’s title is officially recognized as holding authority within a particular geographic or administrative area.
-
C.
hasRulerTitle
Indicates that a ruler holds or is associated with a specific formal title of rulership.
-
D.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
E.
rulerSpecies
Indicates that a particular species serves as the ruling or dominant governing group over another entity or domain.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e2aee081908330a5665fa60482 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.