Triple
T23433091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Cuevas Beach |
E563383
|
entity |
| Predicate | relativeToMajorCity |
P101610
|
FINISHED |
| Object | north of Port of Spain |
—
|
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: north of Port of Spain | Statement: [Las Cuevas Beach, relativeToMajorCity, north of Port of Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToMajorCity Context triple: [Las Cuevas Beach, relativeToMajorCity, north of Port of Spain]
-
A.
distanceFromMajorCity
Indicates the measured distance between a given location and a specified major city.
-
B.
locationRelativeToLargestCity
chosen
Indicates how a place is spatially positioned or oriented in relation to the largest city in a given area or region.
-
C.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
-
D.
adjacentMajorCity
Indicates that one major city is geographically next to or directly bordering another major city.
-
E.
isNearCapitalCity
Indicates that an entity is located close to, or in the immediate vicinity of, a capital city.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d9f0d48190903f43d044bcf2dd |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:49 p.m.