Triple
T17790655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcán Tolimán |
E444149
|
entity |
| Predicate | Cerro de OroLocation |
P128931
|
FINISHED |
| Object | north flank of Volcán Tolimá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: north flank of Volcán Tolimán | Statement: [Volcán Tolimán, Cerro de OroLocation, north flank of Volcán Tolimán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Cerro de OroLocation Context triple: [Volcán Tolimán, Cerro de OroLocation, north flank of Volcán Tolimán]
-
A.
hasRelativePositionOnCerroDeLaSilla
Indicates that one entity has a specific spatial or locational relationship relative to Cerro de la Silla.
-
B.
ianaLocation
Indicates that an entity is associated with a specific geographic or network location identified using an IANA-defined naming or coding scheme.
-
C.
NazcaLinesLocation
Indicates that a location is the site where the Nazca Lines are found or situated.
-
D.
locatedOnEasternSlopeOf
Indicates that one entity is situated on the eastern slope or side of another geographic feature or elevation.
-
E.
medalAtLocation
Indicates that a medal was awarded, received, or is associated with a specific location.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879688908190a5428b1fa7525f62 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:13 a.m.