Triple
T32542800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koningskwestie |
E831755
|
entity |
| Predicate | supportBaseForLeopoldIII |
P115353
|
FINISHED |
| Object | Flanders |
E21312
|
NE 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: Flanders | Statement: [Koningskwestie, supportBaseForLeopoldIII, Flanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportBaseForLeopoldIII Context triple: [Koningskwestie, supportBaseForLeopoldIII, Flanders]
-
A.
reignSupportedBy
Indicates that a ruler’s period of rule is backed, upheld, or sustained by a particular person, group, or power.
-
B.
thirdMonarch
Indicates that the subject is the third monarch in a succession or lineage relative to a specified realm or dynasty.
-
C.
supportedMonarch
Indicates that one entity actively backed, endorsed, or maintained the rule or authority of a particular monarch.
-
D.
monarchOnChristianSide
Indicates that the monarch is aligned with, supports, or belongs to the Christian side in a conflict, alliance, or broader religious-political context.
-
E.
seatOfLiege
chosen
Indicates that a location serves as the primary seat or base of authority for a particular liege or ruling lord.
- F. None of above.
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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34703fcd148190b105a710b1a276b5 |
completed | June 18, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:02 a.m.