Triple
T31202925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godfrey III, Count of Louvain |
E795522
|
entity |
| Predicate | reignStartAsDukeOfLowerLotharingia |
P180977
|
FINISHED |
| Object | 1142 |
—
|
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: 1142 | Statement: [Godfrey III, Count of Louvain, reignStartAsDukeOfLowerLotharingia, 1142]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsDukeOfLowerLotharingia Context triple: [Godfrey III, Count of Louvain, reignStartAsDukeOfLowerLotharingia, 1142]
-
A.
reignAsDukeOfLowerLotharingiaStart
chosen
Indicates the point in time when an individual begins their tenure reigning as Duke of Lower Lotharingia.
-
B.
reignAsDukeOfLorraineStart
Indicates the time at which an individual begins their tenure reigning as Duke of Lorraine.
-
C.
reignStartAsKingOfAustrasia
Indicates the time or event when an individual began their reign as king of Austrasia.
-
D.
reignStartAsKingOfEastFrancia
Indicates the date or event when an individual began their reign as king of East Francia.
-
E.
reignAsDukeFrom
Indicates that an entity holds and exercises the title and authority of duke over a domain starting from a specified time.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 9:09 p.m.