Triple
T12345737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia C6-01 |
E294348
|
entity |
| Predicate | gpsTechnology |
P35891
|
FINISHED |
| Object | A-GPS |
—
|
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: A-GPS | Statement: [Nokia C6-01, gpsTechnology, A-GPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gpsTechnology Context triple: [Nokia C6-01, gpsTechnology, A-GPS]
-
A.
hasNavigationTechnology
chosen
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
B.
trackingTechnology
Indicates that one entity uses or is associated with a technology designed to monitor, record, or follow the behavior, location, or interactions of another entity.
-
C.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
-
D.
locationServices
Indicates that one entity provides, enables, or manages geographic positioning or place-related functionalities for another entity.
-
E.
satelliteSystem
Indicates a relationship where one system functions as a satellite or subordinate system orbiting, supporting, or depending on another primary system.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7a4a448190aa70d66dc2f406c1 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.