Triple
T15336569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N97 |
E366681
|
entity |
| Predicate | supportsAGPS |
P116996
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nokia N97, supportsAGPS, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAGPS Context triple: [Nokia N97, supportsAGPS, true]
-
A.
supportsA-GPS
chosen
Indicates that one entity provides compatibility with or functionality for Assisted GPS (A-GPS) for another entity.
-
B.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
-
C.
supportsGPRS
Indicates that one entity provides or is compatible with GPRS (General Packet Radio Service) functionality for another entity.
-
D.
supportsGSM
Indicates that one entity provides compatibility with or operational support for GSM (Global System for Mobile communications) technology for another entity.
-
E.
supports3G
Indicates that one entity provides or is compatible with 3G mobile network connectivity for another entity or for its operation.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e11b22c81908280efe65acd5454 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.