Triple
T27510812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean theater of the Spanish American wars of independence |
E694404
|
entity |
| Predicate | strategicCity |
P162501
|
FINISHED |
| Object | Bogotá |
—
|
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: Bogotá | Statement: [Andean theater of the Spanish American wars of independence, strategicCity, Bogotá]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicCity Context triple: [Andean theater of the Spanish American wars of independence, strategicCity, Bogotá]
-
A.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
B.
cityOwned
Indicates that something is owned, managed, or under the jurisdiction of a city or municipal government.
-
C.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
-
D.
ruledCity
Indicates that a person or governing entity exercised political authority or control over a specific city.
-
E.
wasStrategicCenterIn
chosen
Indicates that an entity functioned as a key strategic center or hub within a specified context, such as a region, period, or conflict.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 1:16 p.m.