Triple
T35874022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Soledad |
E1037309
|
entity |
| Predicate | typicalStartingDirectionTo |
P31133
|
FINISHED |
| Object | Acatenango summit |
E319540
|
NE 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: Acatenango summit | Statement: [La Soledad, typicalStartingDirectionTo, Acatenango summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartingDirectionTo Context triple: [La Soledad, typicalStartingDirectionTo, Acatenango summit]
-
A.
directionFromStart
Indicates the orientation or path taken moving outward from a defined starting point toward another location or object.
-
B.
approachDirection
chosen
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
C.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
D.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
E.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
- F. None of above.
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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39a304c7fc81909b7e6fe786982e0a |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.