Triple
T30483471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Air |
E775650
|
entity |
| Predicate | successorInLineupTo |
P110538
|
FINISHED |
| Object | MacBook (plastic) series |
—
|
NE NERFINISHED |
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 (plastic) series | Statement: [MacBook Air, successorInLineupTo, MacBook (plastic) series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInLineupTo Context triple: [MacBook Air, successorInLineupTo, MacBook (plastic) series]
-
A.
successorInLineup
chosen
Indicates that one entity immediately follows another in a specified ordered lineup or sequence.
-
B.
successorInLineage
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
C.
successorLine
Indicates that one line directly follows another in a sequence or ordered arrangement.
-
D.
isNextInLineTo
Indicates that one entity is immediately scheduled or positioned to receive something or assume a role after another entity.
-
E.
isNextInLineOfSuccessionTo
Indicates that one entity is the immediate heir or successor designated to take over a position, title, or role when the current holder can no longer occupy it.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 29, 2026, 8:13 p.m.