Triple
T4174326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hainaut |
E86438
|
entity |
| Predicate | frequentBattlegroundIn |
P46035
|
FINISHED |
| Object | European conflicts |
—
|
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: European conflicts | Statement: [Hainaut, frequentBattlegroundIn, European conflicts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentBattlegroundIn Context triple: [Hainaut, frequentBattlegroundIn, European conflicts]
-
A.
oftenBattles
Indicates that one entity frequently engages in conflicts, fights, or confrontations with another entity.
-
B.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
C.
wasKeyBattlegroundDuring
chosen
Indicates that a location served as an important site of conflict or struggle during a specified event or period.
-
D.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
E.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.