Triple
T30300193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel-based Mac |
E770632
|
entity |
| Predicate | firstProductsReleaseYear |
P40835
|
FINISHED |
| Object | 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: 2006 | Statement: [Intel-based Mac, firstProductsReleaseYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstProductsReleaseYear Context triple: [Intel-based Mac, firstProductsReleaseYear, 2006]
-
A.
firstCommercialReleaseYear
chosen
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
-
B.
firstGenerationReleaseDate
Indicates the calendar date on which the first generation or initial version of something was officially released.
-
C.
productionModelDebut
Indicates the event or point in time when a model first enters official production or is publicly released as a production version.
-
D.
firstProductAnnounced
Indicates that an entity is the earliest (chronologically first) product publicly announced by another entity.
-
E.
firstPrototypeYear
Indicates the year in which the first prototype of an entity was created or completed.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01beacf8a88190ac643a75c7a0efc4 |
completed | May 11, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_6a01be152c8c8190bb19d64a683e2aae |
completed | May 11, 2026, 11:31 a.m. |
Created at: April 29, 2026, 7:48 p.m.