Triple
T37659984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fastlane |
E937694
|
entity |
| Predicate | primaryNavigationMethod |
P204313
|
FINISHED |
| Object | horizontal swipes |
—
|
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: horizontal swipes | Statement: [Fastlane, primaryNavigationMethod, horizontal swipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryNavigationMethod Context triple: [Fastlane, primaryNavigationMethod, horizontal swipes]
-
A.
primaryNavigation
Indicates the main navigational relationship or pathway that serves as the primary means of moving between or accessing related entities.
-
B.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
C.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
D.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
E.
primaryRouteOf
Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
- F. None of above. chosen
Provenance (4 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.