Triple
T12746312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 13 Pro |
E304611
|
entity |
| Predicate | positioningSystems |
P106699
|
FINISHED |
| Object | 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: GPS | Statement: [iPhone 13 Pro, positioningSystems, GPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positioningSystems Context triple: [iPhone 13 Pro, positioningSystems, GPS]
-
A.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
B.
designPositioning
Indicates the spatial or conceptual placement of a design element relative to other elements or a defined reference.
-
C.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
D.
positionInWorlds
Indicates that an entity occupies specific spatial coordinates or locations within one or more distinct worlds or environments.
-
E.
positionOnEnvironment
Indicates the spatial placement or location of an entity relative to a surrounding environment or surface.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:27 p.m.