Triple
T30483491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Air |
E775650
|
entity |
| Predicate | firstAppleSiliconModel |
P203893
|
FINISHED |
| Object | MacBook Air (M1, 2020) |
E38962
|
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: MacBook Air (M1, 2020) | Statement: [MacBook Air, firstAppleSiliconModel, MacBook Air (M1, 2020)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppleSiliconModel Context triple: [MacBook Air, firstAppleSiliconModel, MacBook Air (M1, 2020)]
-
A.
appleSiliconGeneration
Indicates the specific Apple Silicon processor generation associated with or used by an entity.
-
B.
firstAppleSoCWith
Indicates that a given Apple system-on-chip (SoC) is the first Apple SoC to feature or introduce a specified component, capability, or characteristic.
-
C.
macOSReleaseDate
Indicates the calendar date on which a specific version of macOS was officially released.
-
D.
firstIntelMacModels
Indicates that the subject is among the earliest Macintosh computer models to use Intel processors.
-
E.
integratedGPUFamily
Indicates that one entity is a member of, or associated with, a particular family or series of integrated graphics processing units.
- F. None of above. chosen
Provenance (5 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0245e917748190bf0a65db538aa66f |
completed | May 11, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2856e777448190beaeb69b0cce341b |
completed | June 9, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a023f7cf7148190af5c2ea501511145 |
completed | May 11, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_6a0245e83d5c8190b3cf9a5ea17c5d9c |
completed | May 11, 2026, 9:11 p.m. |
Created at: April 29, 2026, 8:13 p.m.