Triple
T1271799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixel 6 |
E15725
|
entity |
| Predicate | wirelessTechnology |
P6774
|
FINISHED |
| Object | 5G NR |
—
|
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: 5G NR | Statement: [Pixel 6, wirelessTechnology, 5G NR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wirelessTechnology Context triple: [Pixel 6, wirelessTechnology, 5G NR]
-
A.
wirelessSupportIntroduced
Indicates that support for wireless functionality was added or became available for the first time.
-
B.
supportsWiFiStandard
Indicates that one entity is compatible with and able to operate using a specified Wi-Fi communication standard defined by another entity.
-
C.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
-
D.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
E.
technologicalFeature
chosen
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c06ae7b88190a1e0b5232d84a7b1 |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.