Triple
T24972138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Petit Dauphin |
E624918
|
entity |
| Predicate | hasReferentHouse |
P10994
|
FINISHED |
| Object | House of Bourbon |
—
|
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: House of Bourbon | Statement: [Le Petit Dauphin, hasReferentHouse, House of Bourbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferentHouse Context triple: [Le Petit Dauphin, hasReferentHouse, House of Bourbon]
-
A.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
B.
hasHouseWithin
Indicates that one entity possesses or is associated with a house that is located within the spatial or administrative boundaries of another entity.
-
C.
hasParentHouse
chosen
Indicates that an entity is associated with or belongs to a specific parent house within a hierarchical or familial structure.
-
D.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
E.
hasHouses
Indicates that one entity possesses, controls, or contains one or more houses in relation to another entity or context.
- 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_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 18, 2026, 6:01 a.m.