Triple
T19451093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 15 series |
E486614
|
entity |
| Predicate | materialInStandardModels |
P92637
|
FINISHED |
| Object | aluminum frame |
—
|
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: aluminum frame | Statement: [iPhone 15 series, materialInStandardModels, aluminum frame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialInStandardModels Context triple: [iPhone 15 series, materialInStandardModels, aluminum frame]
-
A.
materialCompatibility
Indicates that two or more materials are suitable to be used together without causing adverse interactions, degradation, or performance issues.
-
B.
materialOptions
chosen
Indicates that there are one or more possible materials that can be chosen or applied in relation to a given entity or context.
-
C.
exampleMaterial
Indicates that something serves as a representative or illustrative material or sample of something else.
-
D.
featuresMaterialType
Indicates that an entity is characterized by or incorporates a specific type of material.
-
E.
materialParameter
Indicates a relationship where a specific parameter or property is associated with, or characterizes, a material in a given context.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.