Triple
T24972131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Petit Dauphin |
E624918
|
entity |
| Predicate | refersToNobleFamily |
P13617
|
FINISHED |
| Object | Bourbon dynasty |
—
|
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: Bourbon dynasty | Statement: [Le Petit Dauphin, refersToNobleFamily, Bourbon dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToNobleFamily Context triple: [Le Petit Dauphin, refersToNobleFamily, Bourbon dynasty]
-
A.
refersToNotableFamily
Indicates that an entity is associated with, or makes reference to, a specific well-known or historically significant family.
-
B.
associatedNobleFamily
chosen
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
C.
refersToPersonWithDynasty
Indicates that one entity makes reference to a person specifically identified or characterized by their association with a particular dynasty.
-
D.
fatherNobleFamily
Indicates that a person’s father belongs to, or is a member of, a specified noble family.
-
E.
usedByNobleFamily
Indicates that something is employed, possessed, or otherwise utilized by a noble family.
- 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_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:01 a.m.