Triple
T13014221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E71 |
E322502
|
entity |
| Predicate | positioningSystem |
P106699
|
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 E71, positioningSystem, A-GPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positioningSystem Context triple: [Nokia E71, positioningSystem, A-GPS]
-
A.
positioningSystems
chosen
Indicates a relationship where systems are used to determine, track, or control the spatial position or location of entities.
-
B.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
C.
designPositioning
Indicates the spatial or conceptual placement of a design element relative to other elements or a defined reference.
-
D.
hasPositioning
Indicates that one entity occupies, is arranged in, or is assigned a specific spatial or relative position with respect to another entity or reference frame.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecbb8f4819094d55eb07cb5ad97 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:50 p.m.