Triple
T15785858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbey of Fécamp |
E382735
|
entity |
| Predicate | postNormanConquestStatus |
P120004
|
FINISHED |
| Object | landholder in England |
—
|
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: landholder in England | Statement: [Abbey of Fécamp, postNormanConquestStatus, landholder in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postNormanConquestStatus Context triple: [Abbey of Fécamp, postNormanConquestStatus, landholder in England]
-
A.
reignAsDukeOfNormandyTo
Indicates that one entity holds and exercises the title and authority of Duke of Normandy over another entity (typically a territory or domain).
-
B.
reignEndAsDukeOfNormandy
Indicates the time or event at which an individual's rule or authority as Duke of Normandy comes to an end.
-
C.
postMonarchyStatus
Indicates the status or condition of an entity after the end or abolition of a monarchy.
-
D.
reignStartAsDukeOfNormandy
Indicates the date or point in time when an individual began their rule holding the title of Duke of Normandy.
-
E.
successorAsDukeOfNormandy
Indicates that one person becomes the next holder of the title Duke of Normandy after another person.
- F. None of above. chosen
Provenance (4 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0540380448190a025338f0e62e6d1 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e006b17f7881908b8c7a37f0af4581 |
completed | April 15, 2026, 9:44 p.m. |
Created at: April 10, 2026, 4:48 a.m.