Triple
T30405421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac OS X on Intel |
E773464
|
entity |
| Predicate | firstPublicHardwareRelease |
P114218
|
FINISHED |
| Object | January 2006 |
—
|
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: January 2006 | Statement: [Mac OS X on Intel, firstPublicHardwareRelease, January 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicHardwareRelease Context triple: [Mac OS X on Intel, firstPublicHardwareRelease, January 2006]
-
A.
firstPublicReleaseDevice
chosen
Indicates that the subject is the device on which something (e.g., a product, feature, or software) was first publicly released.
-
B.
firstProductAnnounced
Indicates that an entity is the earliest (chronologically first) product publicly announced by another entity.
-
C.
firstDeployedIn
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
-
D.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
E.
firstWorkReleaseDate
Indicates the calendar date on which an entity’s earliest or first work was officially released.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a02145017b08190bd424cc647c08d3b |
completed | May 11, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_6a021338e2b08190980c489ee44c18b3 |
completed | May 11, 2026, 5:34 p.m. |
Created at: April 29, 2026, 8:03 p.m.