Triple
T25993631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putot-en-Bessin |
E646424
|
entity |
| Predicate | locatedInHistoricalArea |
P133942
|
FINISHED |
| Object | Normandy landings region |
—
|
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: Normandy landings region | Statement: [Putot-en-Bessin, locatedInHistoricalArea, Normandy landings region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHistoricalArea Context triple: [Putot-en-Bessin, locatedInHistoricalArea, Normandy landings region]
-
A.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
B.
partOfHistoricalArea
chosen
Indicates that one entity is located within or belongs to a designated historical area or heritage zone.
-
C.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
D.
historicallyLocatedNear
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
E.
isInHistoricCenterOf
Indicates that one entity is located within the historic center area of another entity (typically a city or town).
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 22, 2026, 8:57 a.m.