Triple
T18863719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Washington Auto Road |
E461377
|
entity |
| Predicate | followsSideOf |
P31095
|
FINISHED |
| Object | eastern slope of Mount Washington |
—
|
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: eastern slope of Mount Washington | Statement: [Mount Washington Auto Road, followsSideOf, eastern slope of Mount Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSideOf Context triple: [Mount Washington Auto Road, followsSideOf, eastern slope of Mount Washington]
-
A.
followsAlignmentOf
Indicates that one entity adopts or conforms to the alignment, orientation, or positioning established by another entity.
-
B.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
C.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
D.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
E.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a304d4819092f14b7932d01afe |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.