Triple
T21741582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 12.9‑inch iPad Pro (1st generation) |
E536671
|
entity |
| Predicate | hasCellularVariant |
P99395
|
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: [12.9‑inch iPad Pro (1st generation), hasCellularVariant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCellularVariant Context triple: [12.9‑inch iPad Pro (1st generation), hasCellularVariant, true]
-
A.
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.
-
B.
hasCellularComponent
Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
-
C.
cellularOptions
chosen
Indicates that one entity specifies or provides available cellular network or mobile connectivity options for another entity.
-
D.
hasCellService
Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
-
E.
hasSIMType
Indicates that an entity uses or is associated with a specific type or category of SIM (Subscriber Identity Module).
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a7250d48190aa63f89db017ef70 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.