Triple
T34539316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Raspe |
E886759
|
entity |
| Predicate | succeededByAsAntiKing |
P201281
|
FINISHED |
| Object | William II of Holland |
—
|
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: William II of Holland | Statement: [Henry Raspe, succeededByAsAntiKing, William II of Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByAsAntiKing Context triple: [Henry Raspe, succeededByAsAntiKing, William II of Holland]
-
A.
servedKing
Indicates that one entity performed duties or services in allegiance or obedience to a king.
-
B.
selectedAsKing
Indicates that an entity has been chosen or appointed to hold the position or role of king.
-
C.
opponentKing
Indicates that one entity is the king belonging to the opposing or rival side of the other entity.
-
D.
hasCheckOnKings
Indicates that one player’s move currently places the opposing king in check.
-
E.
reignAsAntiKingStart
Indicates the point in time when an individual begins an illegitimate or rival reign as an anti-king in opposition to a recognized monarch.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69ffe6130698819099328fce92bb2784 |
completed | May 10, 2026, 1:57 a.m. |
Created at: May 1, 2026, 2:02 a.m.