Triple
T34510432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 85 |
E886002
|
entity |
| Predicate | usedForNavigationBy |
P14917
|
FINISHED |
| Object | motorists |
—
|
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: motorists | Statement: [SR 85, usedForNavigationBy, motorists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForNavigationBy Context triple: [SR 85, usedForNavigationBy, motorists]
-
A.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
B.
hasNavigationUse
chosen
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
C.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
-
D.
designedForNavigationImprovement
Indicates that something was intentionally created or configured to enhance the ease, efficiency, or accuracy of navigation.
-
E.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 1, 2026, 2:01 a.m.