Triple
T26452041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Turkish invasion of Cyprus |
E665375
|
entity |
| Predicate | keyLandingArea |
P8974
|
FINISHED |
| Object | Kyrenia |
—
|
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: Kyrenia | Statement: [First Turkish invasion of Cyprus, keyLandingArea, Kyrenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyLandingArea Context triple: [First Turkish invasion of Cyprus, keyLandingArea, Kyrenia]
-
A.
keyLandingSite
Indicates a location that serves as the primary or designated site where something (such as a vehicle, object, or mission) is intended to land or touch down.
-
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.
keyTransitArea
Indicates that a location functions as a primary passage or hub through which movement or transport between other areas is concentrated or facilitated.
-
D.
partOfLandingSector
Indicates that one entity constitutes a component or subdivision within a larger landing sector.
-
E.
intendedLandingRegion
Indicates the geographic area or region where something is planned or expected to 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612661bf08190897f910a6ade77cc |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:06 a.m.