Triple
T25679638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caana |
E643902
|
entity |
| Predicate | isMostProminentStructureAt |
P57478
|
FINISHED |
| Object | Caracol |
—
|
NE NERFINISHED |
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: Caracol | Statement: [Caana, isMostProminentStructureAt, Caracol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMostProminentStructureAt Context triple: [Caana, isMostProminentStructureAt, Caracol]
-
A.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
hasHighestStructure
Indicates that an entity possesses the tallest or most elevated structural feature compared to all other relevant entities in a given context.
-
C.
elevatedInProminenceBy
Indicates that an entity’s prominence, status, or visibility is increased as a result of the actions or influence of another entity.
-
D.
isMostTopographicallyProminentIn
Indicates that an entity has the greatest topographic prominence within a specified area or group, exceeding that of all comparable entities.
-
E.
isTallestStructureIn
chosen
Indicates that the subject is the tallest structure located within the specified place or area.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb77c3a08190b63e811dd21989fd |
completed | May 2, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 7:45 p.m.