Triple
T15158777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Pixel 6 Pro |
E362150
|
entity |
| Predicate | esimSupport |
P49173
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Google Pixel 6 Pro, esimSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esimSupport Context triple: [Google Pixel 6 Pro, esimSupport, yes]
-
A.
supportsEsim
chosen
Indicates that one entity provides compatibility with, or the ability to use, an embedded SIM (eSIM) for another entity.
-
B.
hasSIMType
Indicates that an entity uses or is associated with a specific type or category of SIM (Subscriber Identity Module).
-
C.
hasSIMConfiguration
Indicates that an entity is associated with or assigned a specific SIM card configuration or setup.
-
D.
hasCellularComponent
Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
-
E.
hasCellularModel
Indicates that one entity serves as a cellular (cell-based) model or system used to study, represent, or simulate the biological properties or behavior 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060dd71881908ecc4a4f52d438a5 |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.