Triple
T32639586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Beaumont |
E834442
|
entity |
| Predicate | hasTitleHolderHouse |
P23794
|
FINISHED |
| Object | House of Évreux |
—
|
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 Évreux | Statement: [Duke of Beaumont, hasTitleHolderHouse, House of Évreux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleHolderHouse Context triple: [Duke of Beaumont, hasTitleHolderHouse, House of Évreux]
-
A.
hasTitleHolderResidence
Indicates that a specified residence is the official home or dwelling place of the current holder of a particular title.
-
B.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
C.
titleHolderHouse
chosen
Indicates that a particular house or noble family holds or is associated with a specific title.
-
D.
hasTitleHolderTrait
Indicates that an entity possesses a characteristic or status specifically associated with holding a particular title.
-
E.
hasTitleHolderSpecies
Indicates that a particular species currently holds or is designated as the title holder for a specified title, rank, or distinction.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 1, 2026, 1:07 a.m.