Triple
T33108306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royaume d’Yvetot |
E847253
|
entity |
| Predicate | régionHistorique |
P915
|
FINISHED |
| Object | Normandie |
—
|
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: Normandie | Statement: [Royaume d’Yvetot, régionHistorique, Normandie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: régionHistorique Context triple: [Royaume d’Yvetot, régionHistorique, Normandie]
-
A.
historicalRegion
chosen
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
B.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
C.
historicalFocusRegion
Indicates that an entity’s primary historical attention, study, or activity is centered on a particular geographic region.
-
D.
regionHistory
Indicates that there exists a historical or past association between a subject and a specific geographic or administrative region.
-
E.
historicalStatusOfRegion
Indicates the historical political or administrative status that a region held during a specific past period.
- 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.