Triple
T21552415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7th generation iPad |
E531794
|
entity |
| Predicate | supportsAppleArcade |
P103411
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [7th generation iPad, supportsAppleArcade, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAppleArcade Context triple: [7th generation iPad, supportsAppleArcade, yes]
-
A.
allowsAppleArcadeSharing
Indicates that an entity permits Apple Arcade access or subscriptions to be shared with other users, such as through family or group sharing.
-
B.
supportsGames
chosen
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
C.
hasArcades
Indicates that one entity features or contains arcaded structures (a series of arches or covered passageways) associated with another entity.
-
D.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
-
E.
homeArenaSupported
Indicates that an entity is supported or hosted in its designated home arena or primary venue.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59375f481909d9e2b66d18c7c32 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.