Triple
T235931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Elbrus |
E4824
|
entity |
| Predicate | standardRouteFrom |
P6298
|
FINISHED |
| Object | south side |
—
|
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: south side | Statement: [Mount Elbrus, standardRouteFrom, south side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRouteFrom Context triple: [Mount Elbrus, standardRouteFrom, south side]
-
A.
primaryRoute
chosen
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
B.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
C.
standardFormBasedOn
Indicates that one entity’s standard or canonical form is derived from, defined by, or constructed on the basis of another entity.
-
D.
standardFormBasedIn
Indicates that a standardized form or format is established, defined, or grounded in a particular source, basis, or reference framework.
-
E.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25ccab7648190be6e4f5febc1e313 |
completed | Feb. 28, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69a25b5dc640819092669575731c393f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.