Triple
T3472990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Pixel 4 |
E73305
|
entity |
| Predicate | supportsEsim |
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 4, supportsEsim, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEsim Context triple: [Google Pixel 4, supportsEsim, yes]
-
A.
supportsRoamingWith
Indicates that one entity enables or is compatible with another entity’s ability to operate or be accessed while roaming across different networks or locations.
-
B.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
C.
hasSatelliteTerminal
Indicates that an entity is equipped with or connected to a satellite communication terminal.
-
D.
supportsMarket
Indicates that one entity provides resources, infrastructure, or conditions that enable or facilitate the functioning or growth of a market associated with another entity.
-
E.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3e03e081908aa09291bbf351bd |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:17 p.m.