Triple
T30001614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ProMotion |
E762183
|
entity |
| Predicate | firstIntroducedOn |
P18472
|
FINISHED |
| Object | iPad Pro (2017) |
—
|
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: iPad Pro (2017) | Statement: [ProMotion, firstIntroducedOn, iPad Pro (2017)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroducedOn Context triple: [ProMotion, firstIntroducedOn, iPad Pro (2017)]
-
A.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
B.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
C.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
D.
firstAppearedAt
chosen
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
E.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 |
completed | May 11, 2026, 6:19 a.m. |
| PD | Predicate disambiguation | batch_6a01748d65248190ac3d9adfa9d0b274 |
completed | May 11, 2026, 6:17 a.m. |
Created at: April 29, 2026, 6:41 p.m.