Triple
T19451523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Go for Apple Watch |
E486622
|
entity |
| Predicate | requiresApp |
P11910
|
FINISHED |
| Object | Pokémon Go for iOS |
—
|
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: Pokémon Go for iOS | Statement: [Pokémon Go for Apple Watch, requiresApp, Pokémon Go for iOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresApp Context triple: [Pokémon Go for Apple Watch, requiresApp, Pokémon Go for iOS]
-
A.
requiresApplicationTo
Indicates that one entity can only access, use, or obtain another entity if a formal application or request process is completed.
-
B.
requiresApplicationOf
Indicates that performing one entity or process depends on actively applying or using another entity, method, or resource.
-
C.
requiresSoftware
chosen
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
D.
mandatoryApplicationFrom
Indicates that one entity is required to submit an application to another entity as a compulsory condition or step.
-
E.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63392aab08190aab09b7c356e5b10 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.