Triple
T2829006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noshaq |
E62190
|
entity |
| Predicate | standardRouteVia |
P11333
|
FINISHED |
| Object | southwest ridge |
—
|
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: southwest ridge | Statement: [Noshaq, standardRouteVia, southwest ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRouteVia Context triple: [Noshaq, standardRouteVia, southwest ridge]
-
A.
routeVia
chosen
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
B.
parallelRoute
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
-
C.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
D.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
E.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abde97168c8190b31122b2ad9fdebf |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.