Triple
T1309435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicosia |
E27954
|
entity |
| Predicate | isDividedCity |
P6497
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nicosia, isDividedCity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDividedCity Context triple: [Nicosia, isDividedCity, true]
-
A.
hasCivilDivision
Indicates that one administrative or political entity is subdivided into, or is associated with, a specific civil division (such as a county, district, or municipality).
-
B.
dividedBetween
chosen
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
C.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
D.
isSubProvincialCity
Indicates that a city holds a sub-provincial administrative status, ranking below a province but above ordinary prefecture-level cities in the governmental hierarchy.
-
E.
isCoreCity
Indicates that a city serves as a primary, central, or most important urban area within a larger region, system, or network.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c15490a88190872c3d2698a8f9c9 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.