Triple

T27612985
Position Surface form Disambiguated ID Type / Status
Subject Office JavaScript API E700371 entity
Predicate supportsApplication P15794 FINISHED
Object Office on iPad
Office on iPad is the mobile version of Microsoft Office optimized for Apple’s iPad, providing touch-friendly access to Word, Excel, PowerPoint, and related productivity features.
E193793 NE 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: Office on iPad | Statement: [Office JavaScript API, supportsApplication, Office on iPad]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Office on iPad
Triple: [Office JavaScript API, supportsApplication, Office on iPad]
Generated description
Office on iPad is the mobile version of Microsoft Office optimized for Apple’s iPad, providing touch-friendly access to Word, Excel, PowerPoint, and related productivity features.

Provenance (5 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_69ef6a4f1d9c8190b0705acda054368d completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f630d5c31081909d20e8165cc0515f completed May 2, 2026, 5:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12d0edc084819086456d76708f614c completed May 24, 2026, 10:20 a.m.
NEDg Description generation batch_6a12d234d9448190934052fbbf66e999 completed May 24, 2026, 10:25 a.m.
NED2 Entity disambiguation (via description) batch_6a12d2c4f3788190bb09cedbf1c29be3 completed May 24, 2026, 10:28 a.m.
Created at: April 27, 2026, 2:11 p.m.