Triple
T21219224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPad Pro |
E522919
|
entity |
| Predicate | firstGenerationDisplaySize |
P143246
|
FINISHED |
| Object | 12.9-inch |
—
|
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: 12.9-inch | Statement: [iPad Pro, firstGenerationDisplaySize, 12.9-inch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGenerationDisplaySize Context triple: [iPad Pro, firstGenerationDisplaySize, 12.9-inch]
-
A.
firstGeneration
Indicates that an entity belongs to the first generation within a defined lineage, sequence, or series relative to other related entities.
-
B.
firstGenerationBasedOn
Indicates that one entity is the initial or earliest version derived or developed from another entity as its basis.
-
C.
firstGenerationStart
Indicates the point in time or event at which the first generation in a sequence, lineage, or series begins.
-
D.
firstGenerationName
Indicates that the specified name is assigned to or associated with the first generation in a sequence, lineage, or series.
-
E.
firstGenerationReleaseDate
Indicates the calendar date on which the first generation or initial version of something was officially released.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73476d93481909c6c99dcc0b16123 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:43 p.m.