Triple
T33108324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royaume d’Yvetot |
E847253
|
entity |
| Predicate | souverainTitre |
P163921
|
FINISHED |
| Object | roi d’Yvetot |
—
|
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: roi d’Yvetot | Statement: [Royaume d’Yvetot, souverainTitre, roi d’Yvetot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: souverainTitre Context triple: [Royaume d’Yvetot, souverainTitre, roi d’Yvetot]
-
A.
coSovereignTitle
Indicates that two or more entities share the same sovereign authority or ruling title jointly.
-
B.
sovereignTitleUntil
Indicates that an entity held a particular sovereign title or rulership status continuously up to a specified end date or point in time.
-
C.
monarchTitleInProvince
Indicates that a monarch holds a specific royal title associated with a particular province or territorial subdivision.
-
D.
monarchicTitleHolderOf
chosen
Indicates that one entity holds a monarchic title associated with another entity (such as a realm, position, or office).
-
E.
royalTitularyFeature
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6e86f7c8190836278fd08e5cfed |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.