Triple
T27161158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varosha (abandoned quarter) |
E682663
|
entity |
| Predicate | notableFeatureBefore1974 |
P200556
|
FINISHED |
| Object | high-rise hotels along the beach |
—
|
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: high-rise hotels along the beach | Statement: [Varosha (abandoned quarter), notableFeatureBefore1974, high-rise hotels along the beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeatureBefore1974 Context triple: [Varosha (abandoned quarter), notableFeatureBefore1974, high-rise hotels along the beach]
-
A.
statusBefore1994
Indicates that a particular status or condition held by an entity was in effect prior to the year 1994.
-
B.
tourismStatusBefore1974
Indicates the tourism-related condition or classification that applied to an entity prior to the year 1974.
-
C.
regionBefore1996
Indicates that a region existed or was defined prior to the year 1996.
-
D.
statusBefore1989
Indicates that the referenced status or condition applied to the entity prior to the year 1989.
-
E.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
- F. None of above. chosen
Provenance (4 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69ff965eef90819097499d1f0542378c |
completed | May 9, 2026, 8:17 p.m. |
Created at: April 27, 2026, 9:18 a.m.