Triple
T1775132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firestorm |
E38959
|
entity |
| Predicate | usedInDeviceFamily |
P31538
|
FINISHED |
| Object | Mac computers with Apple silicon |
—
|
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: Mac computers with Apple silicon | Statement: [Firestorm, usedInDeviceFamily, Mac computers with Apple silicon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDeviceFamily Context triple: [Firestorm, usedInDeviceFamily, Mac computers with Apple silicon]
-
A.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
B.
usedByFamily
Indicates that something is regularly utilized or consumed by a family as a group.
-
C.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
D.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
E.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab17e368048190b7b73d156400f772 |
completed | March 6, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69aa61cd4c1c8190a8dff391f5642bfe |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab17d0a644819087e6ce39d6c60da5 |
completed | March 6, 2026, 6:07 p.m. |
Created at: March 4, 2026, 7:31 p.m.