Triple
T27263003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caracolí |
E687817
|
entity |
| Predicate | isLocatedToThe |
P171423
|
FINISHED |
| Object | east of Medellín |
—
|
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: east of Medellín | Statement: [Caracolí, isLocatedToThe, east of Medellín]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedToThe Context triple: [Caracolí, isLocatedToThe, east of Medellín]
-
A.
isLocalTo
Indicates that one entity is geographically or contextually situated near, or within the same local area or scope as, another entity.
-
B.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
C.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 10:54 a.m.