Triple
T8415035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple A11 Bionic |
E198711
|
entity |
| Predicate | supportsMetalVersion |
P82047
|
FINISHED |
| Object | Metal 2 |
—
|
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: Metal 2 | Statement: [Apple A11 Bionic, supportsMetalVersion, Metal 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMetalVersion Context triple: [Apple A11 Bionic, supportsMetalVersion, Metal 2]
-
A.
supportsMetalFXUpscaling
Indicates that one entity provides compatibility with or the ability to use MetalFX upscaling functionality for another entity.
-
B.
appleSiliconGeneration
Indicates the specific Apple Silicon processor generation associated with or used by an entity.
-
C.
supports3DAcceleration
Indicates that one entity provides or enables hardware- or software-based 3D graphics acceleration for another entity.
-
D.
supportsHardwareRayTracing
Indicates that one entity provides or enables hardware-level ray tracing capabilities for another entity or within a given context.
-
E.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e443a08190983d9a0a61e0f781 |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:06 p.m.