Triple
T28617124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows App Certification Kit |
E724296
|
entity |
| Predicate | performsTest |
P5348
|
FINISHED |
| Object | app manifest validation |
—
|
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 manifest validation | Statement: [Windows App Certification Kit, performsTest, app manifest validation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsTest Context triple: [Windows App Certification Kit, performsTest, app manifest validation]
-
A.
performsAs
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
B.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
C.
tests
chosen
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
D.
testConducted
Indicates that a specific test or examination has been performed or carried out on an entity.
-
E.
testingConductedBy
Indicates that a testing activity or process is performed, carried out, or overseen by a specified agent or organization.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 4:32 a.m.