Triple
T8415029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple A11 Bionic |
E198711
|
entity |
| Predicate | neuralEngine |
P11233
|
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: [Apple A11 Bionic, neuralEngine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neuralEngine Context triple: [Apple A11 Bionic, neuralEngine, yes]
-
A.
neuralEngineType
Indicates the specific kind or category of neural processing engine associated with or used by an entity.
-
B.
neuralEnginePerformance
Indicates the level or efficiency of processing capability provided by a neural engine in performing AI or machine-learning tasks.
-
C.
integratesNeuralEngine
chosen
Indicates that one entity incorporates or embeds a neural processing engine within its overall system or architecture.
-
D.
neuralEngineCores
Indicates the number or configuration of neural engine processing cores associated with a given hardware or system.
-
E.
NeuralEngineUseCases
Indicates the various tasks, scenarios, or applications in which a neural engine is employed or leveraged.
- 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_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. |
Created at: March 30, 2026, 6:06 p.m.