Triple
T32542801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koningskwestie |
E831755
|
entity |
| Predicate | oppositionStronghold |
P46785
|
FINISHED |
| Object | Wallonia |
—
|
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: Wallonia | Statement: [Koningskwestie, oppositionStronghold, Wallonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositionStronghold Context triple: [Koningskwestie, oppositionStronghold, Wallonia]
-
A.
traditionalPartyStronghold
Indicates that a particular area or region has historically and consistently provided strong electoral support for a traditional or long-established political party.
-
B.
opposedSiegeBy
Indicates that one party actively resisted, countered, or worked against another party’s siege.
-
C.
strongholdOf
chosen
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
D.
opposedFortification
Indicates that one entity actively resisted, challenged, or worked against the strengthening or fortifying of another entity or location.
-
E.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:02 a.m.