Triple
T351958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Sea Lion |
E7461
|
entity |
| Predicate | plannedLandingArea |
P8974
|
FINISHED |
| Object | southern coast of England |
—
|
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: southern coast of England | Statement: [Operation Sea Lion, plannedLandingArea, southern coast of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedLandingArea Context triple: [Operation Sea Lion, plannedLandingArea, southern coast of England]
-
A.
dateOfLanding
Indicates the specific calendar date on which a landing event took place.
-
B.
landingArea
chosen
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
-
C.
numberOfCrewedLandings
Indicates the count of distinct landing events that involved a crewed (human-occupied) spacecraft.
-
D.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
E.
codenameOfLandings
Indicates that one entity is the codename assigned to a specific set of landings or landing operations.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7f1be88190964ddcbb6a05f021 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.