Triple
T17174506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginkelse Heide |
E416823
|
entity |
| Predicate | landingZoneFor |
P8974
|
FINISHED |
| Object | British paratroopers |
—
|
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 paratroopers | Statement: [Ginkelse Heide, landingZoneFor, British paratroopers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingZoneFor Context triple: [Ginkelse Heide, landingZoneFor, British paratroopers]
-
A.
landingArea
chosen
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
-
B.
landingConfiguration
Indicates the specific arrangement or setup used for an entity’s landing phase or landing operation.
-
C.
landingPlace
Indicates the location or surface where something or someone comes down to rest after moving through the air or space.
-
D.
intendedLandingRegion
Indicates the geographic area or region where something is planned or expected to land.
-
E.
startingZoneFor
Indicates the zone or area where an entity initially begins, is placed, or starts its activity or process.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0c329081909f118bd4b7be8653 |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.