Triple
T16152520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracy-sur-Mer |
E391948
|
entity |
| Predicate | locatedInMilitaryConflictRegion |
P34508
|
FINISHED |
| Object | Normandy landings area |
—
|
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: Normandy landings area | Statement: [Tracy-sur-Mer, locatedInMilitaryConflictRegion, Normandy landings area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMilitaryConflictRegion Context triple: [Tracy-sur-Mer, locatedInMilitaryConflictRegion, Normandy landings area]
-
A.
locatedOnSideOfConflict
Indicates that an entity is positioned or aligned on a particular side or faction within a conflict.
-
B.
basedInDuringConflict
Indicates that an entity is located or headquartered in a particular place for the duration of a specified conflict or war.
-
C.
regionOfConflict
chosen
Indicates that a specified region is the location where a particular conflict or dispute takes place.
-
D.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
-
E.
locatedInDisputedTerritory
Indicates that an entity is situated within a geographic area whose sovereignty or ownership is contested between two or more parties.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d98d08c8190a15d4aee40d47220 |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.