Triple
T12486880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowdon Ranger Path |
E298455
|
entity |
| Predicate | startsOnSideOf |
P86049
|
FINISHED |
| Object | western flank of Snowdon |
—
|
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: western flank of Snowdon | Statement: [Snowdon Ranger Path, startsOnSideOf, western flank of Snowdon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsOnSideOf Context triple: [Snowdon Ranger Path, startsOnSideOf, western flank of Snowdon]
-
A.
wasOnSideOf
Indicates that one entity supported, aligned with, or took the same side as another entity in a conflict, dispute, or opposing situation.
-
B.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
C.
onSide
chosen
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
D.
playsOnSideOfBall
Indicates that one entity participates in a game or sport on a particular side or unit of the ball (e.g., offense or defense).
-
E.
singleSideOf
Indicates that one entity constitutes a single side or face of another entity, typically within a larger multi-sided structure or object.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.