Triple
T33108308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royaume d’Yvetot |
E847253
|
entity |
| Predicate | statutPolitique |
P196919
|
FINISHED |
| Object | seigneurie autonome |
—
|
LITERAL FINISHED |
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: seigneurie autonome | Statement: [Royaume d’Yvetot, statutPolitique, seigneurie autonome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statutPolitique Context triple: [Royaume d’Yvetot, statutPolitique, seigneurie autonome]
-
A.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
B.
politicalState
chosen
Indicates the political condition, status, or governance situation that an entity is currently under or associated with.
-
C.
parliamentaryStatus
Indicates the relationship of whether and how an entity is formally recognized or holds standing within a parliamentary system or body.
-
D.
politicalStatusRepresented
Indicates that an entity’s political status is expressed, symbolized, or officially represented by another entity.
-
E.
politicalForm
Indicates the type or structure of governance or political organization that characterizes an entity.
- 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_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 1, 2026, 1:26 a.m.