Triple
T13096439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geoffrey V, Count of Anjou |
E310600
|
entity |
| Predicate | reignAsCountOfAnjouFrom |
P108020
|
FINISHED |
| Object | 1129 |
—
|
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: 1129 | Statement: [Geoffrey V, Count of Anjou, reignAsCountOfAnjouFrom, 1129]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsCountOfAnjouFrom Context triple: [Geoffrey V, Count of Anjou, reignAsCountOfAnjouFrom, 1129]
-
A.
successorAsDukeOfAnjou
Indicates that one entity became the next holder of the title Duke of Anjou after another entity.
-
B.
reignAsDukeOfBrittanyStart
Indicates the point in time when an individual begins their tenure or rule as the Duke of Brittany.
-
C.
reignAsDauphinFrom
Indicates the period during which a person held and exercised the title and role of Dauphin, starting from a specified time.
-
D.
reignAsDauphinTo
Indicates that one person holds and exercises the title and role of Dauphin (heir apparent to the French throne) in relation to a specific monarch or royal line.
-
E.
reignStartAsDukeOfNormandy
Indicates the date or point in time when an individual began their rule holding the title of Duke of Normandy.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9814e88a0819088418c792ce7aa57 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:03 p.m.