Triple
T13097272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3120 |
E310622
|
entity |
| Predicate | navigationKey |
P108028
|
FINISHED |
| Object | 4-way navigation key |
—
|
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: 4-way navigation key | Statement: [Nokia 3120, navigationKey, 4-way navigation key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationKey Context triple: [Nokia 3120, navigationKey, 4-way navigation key]
-
A.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
B.
navigationSupport
Indicates that one entity provides assistance, guidance, or tools to help another entity navigate or find its way.
-
C.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
D.
navigationRole
Indicates that one entity serves as a navigational aid, control, or function that helps users move through or orient themselves within another entity (such as an interface, document, or environment).
-
E.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9814e88a0819088418c792ce7aa57 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:04 p.m.