Triple
T30127858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochnagar Crater memorial site |
E765749
|
entity |
| Predicate | onBattlefieldOf |
P39414
|
FINISHED |
| Object | Battle of the Somme |
—
|
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: Battle of the Somme | Statement: [Lochnagar Crater memorial site, onBattlefieldOf, Battle of the Somme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onBattlefieldOf Context triple: [Lochnagar Crater memorial site, onBattlefieldOf, Battle of the Somme]
-
A.
battlefieldOf
chosen
Indicates that a location is the site where a particular battle or military engagement took place.
-
B.
primaryBattlefieldOf
Indicates that a specified location serves as the main or most significant battlefield where a particular conflict or war primarily took place.
-
C.
battlefieldSector
Indicates a specific area or zone of a battlefield in which a military unit, action, or event is located or occurs.
-
D.
notableBattlefield
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
-
E.
battlefieldLocatedIn
Indicates that a battlefield is situated within or belongs to a specific geographic or administrative location.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e4586988190ad89b72dd2af3797 |
completed | May 2, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:14 p.m.