Triple
T24972139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Petit Dauphin |
E624918
|
entity |
| Predicate | hasReferentFather |
P172314
|
FINISHED |
| Object | Louis, Grand Dauphin |
—
|
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: Louis, Grand Dauphin | Statement: [Le Petit Dauphin, hasReferentFather, Louis, Grand Dauphin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferentFather Context triple: [Le Petit Dauphin, hasReferentFather, Louis, Grand Dauphin]
-
A.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
B.
hasFatherFigure
Indicates that one entity serves as a paternal or father-like figure to another entity, regardless of biological relation.
-
C.
hasMemberFather
Indicates that an entity is a member of a group or organization by virtue of their father’s membership or paternal relationship.
-
D.
hasHostFather
Indicates a relationship where one person serves as the host father of another, typically in a hosting or exchange context.
-
E.
hasFatherPosition
Indicates that the position, role, or job held by an entity’s father is being specified or linked to that entity.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 18, 2026, 6:01 a.m.