Triple
T12086542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 12 Pro Max |
E287819
|
entity |
| Predicate | displayMarketingName |
P24366
|
FINISHED |
| Object | Super Retina XDR |
—
|
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: Super Retina XDR | Statement: [iPhone 12 Pro Max, displayMarketingName, Super Retina XDR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayMarketingName Context triple: [iPhone 12 Pro Max, displayMarketingName, Super Retina XDR]
-
A.
marketingNameOf
chosen
Indicates that one entity is the marketing or brand name used to promote or refer to another entity.
-
B.
resolutionMarketingName
Indicates the marketed or consumer-facing name used to describe a product’s resolution.
-
C.
originalMarketingName
Indicates the original marketing or brand name under which an entity (such as a product or service) was first promoted or sold.
-
D.
marketingNameEmphasizes
Indicates that a marketing name highlights or draws special attention to a particular feature, attribute, or aspect of something.
-
E.
marketingNameAfterRelease
Indicates that an entity receives or is assigned a marketing name only after its official release.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.