Triple
T21219249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPad Pro |
E522919
|
entity |
| Predicate | runsSoftware |
P143248
|
FINISHED |
| Object | App Store applications |
—
|
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: App Store applications | Statement: [iPad Pro, runsSoftware, App Store applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsSoftware Context triple: [iPad Pro, runsSoftware, App Store applications]
-
A.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
-
B.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
C.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
D.
runsWith
Indicates that one entity runs together alongside another entity, typically at the same time and place.
-
E.
runs
Indicates that an entity moves swiftly on foot, typically using its legs in a continuous, rapid motion.
- 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.