Triple
T36220063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Battle of the Scarpe |
E1047820
|
entity |
| Predicate | countryOfBattlefield |
P133064
|
FINISHED |
| Object | France |
E861
|
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: France | Statement: [Third Battle of the Scarpe, countryOfBattlefield, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfBattlefield Context triple: [Third Battle of the Scarpe, countryOfBattlefield, France]
-
A.
countryDuringBattle
Indicates that a specified country was involved in or existed as a relevant participant or context during a particular battle.
-
B.
countryOfBattlefieldToday
chosen
Indicates the country in which the battlefield is located in the present day, regardless of its historical political status.
-
C.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
D.
countryForWhichFought
Indicates the country on whose behalf or under whose authority an entity participated in a conflict or war.
-
E.
battlefieldLocatedIn
Indicates that a battlefield is situated within or belongs to a specific geographic or administrative location.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02f10505988190be5fd57566a90e0f |
completed | May 12, 2026, 9:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a393411cf2481909563dab50468a194 |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a02f03a8c1481909e137e270119f7ef |
completed | May 12, 2026, 9:17 a.m. |
Created at: May 3, 2026, 4:09 p.m.