Triple
T29183279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple T2 |
E739798
|
entity |
| Predicate | handlesInterface |
P170734
|
FINISHED |
| Object | internal microphones (on supported Macs) |
—
|
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: internal microphones (on supported Macs) | Statement: [Apple T2, handlesInterface, internal microphones (on supported Macs)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesInterface Context triple: [Apple T2, handlesInterface, internal microphones (on supported Macs)]
-
A.
handles
Indicates that one entity is responsible for dealing with, managing, or taking care of another entity or task.
-
B.
handlesFrom
Indicates that one entity is responsible for managing, processing, or dealing with something originating from another entity.
-
C.
coversInterface
Indicates that one entity provides or implements the functionality defined by a specified interface.
-
D.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
-
E.
providesInterfaceBetween
Indicates that one entity serves as an intermediary interface enabling interaction or communication between two other entities or systems.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 28, 2026, 11:58 a.m.