Triple
T30300221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel-based Mac |
E770632
|
entity |
| Predicate | supportsFirmwareType |
P24486
|
FINISHED |
| Object | EFI |
E299191
|
NE 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: EFI | Statement: [Intel-based Mac, supportsFirmwareType, EFI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFirmwareType Context triple: [Intel-based Mac, supportsFirmwareType, EFI]
-
A.
requiresFirmware
Indicates that one entity depends on specific firmware being present or installed on another entity in order to function or be valid.
-
B.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
C.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
D.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
firmwareUpgradable
Indicates that a device’s firmware can be updated or replaced after deployment, typically through software-based upgrade mechanisms.
- F. None of above.
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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a276f0c439081909386911de1a99509 |
completed | June 9, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:48 p.m.