Triple
T30799221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lidra Caddesi |
E784318
|
entity |
| Predicate | wasClosedAsCrossingPointDuring |
P117464
|
FINISHED |
| Object | intercommunal conflict in Cyprus |
—
|
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: intercommunal conflict in Cyprus | Statement: [Lidra Caddesi, wasClosedAsCrossingPointDuring, intercommunal conflict in Cyprus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasClosedAsCrossingPointDuring Context triple: [Lidra Caddesi, wasClosedAsCrossingPointDuring, intercommunal conflict in Cyprus]
-
A.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
-
B.
crossingOpened
Indicates that a crossing (such as a road, rail, or pedestrian crossing) has been opened or made available for passage.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
hasNearbyCrossingPoint
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
-
E.
closedAsBorderCrossing
chosen
Indicates that a location previously used as a border crossing has been officially closed and is no longer available for crossing.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6903998008190a77f8503d88c50d8 |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:42 p.m.