Triple
T3421002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Pixel 3 |
E72113
|
entity |
| Predicate | eSIMSupport |
P36910
|
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 3, eSIMSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eSIMSupport Context triple: [Google Pixel 3, eSIMSupport, yes]
-
A.
connectivityFeatures
chosen
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
B.
hasCellService
Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
-
C.
carrierOf
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys another entity.
-
D.
hasSatelliteTerminal
Indicates that an entity is equipped with or connected to a satellite communication terminal.
-
E.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94eb9e8819087a525df4550914b |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.