Triple
T766864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arromanches-les-Bains |
E16193
|
entity |
| Predicate | wasLandingZoneFor |
P8974
|
FINISHED |
| Object | British forces on D-Day |
—
|
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: British forces on D-Day | Statement: [Arromanches-les-Bains, wasLandingZoneFor, British forces on D-Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLandingZoneFor Context triple: [Arromanches-les-Bains, wasLandingZoneFor, British forces on D-Day]
-
A.
landedOnBy
Indicates that one entity has come down to rest upon or make contact with the surface of another entity.
-
B.
locatedInSkyRegion
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
C.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
D.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
E.
landingArea
chosen
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a765ba688190ab328bb159583077 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a5074c788190a74fc20ad24e2d26 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.