Triple
T9021334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocas de Suesca |
E215729
|
entity |
| Predicate | isTrainingGroundFor |
P42544
|
FINISHED |
| Object | Colombian climbers |
—
|
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: Colombian climbers | Statement: [Rocas de Suesca, isTrainingGroundFor, Colombian climbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTrainingGroundFor Context triple: [Rocas de Suesca, isTrainingGroundFor, Colombian climbers]
-
A.
trainingGroundFor
chosen
Indicates that one entity serves as a place or context where another entity is trained, prepared, or developed.
-
B.
trainingGround
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
-
C.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
-
D.
trainingUnder
Indicates that one entity is receiving instruction, guidance, or mentorship from another, typically in a subordinate or apprentice-like capacity.
-
E.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a43add08190983b7ac88576fd7e |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.