Triple
T27750273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Help |
E702095
|
entity |
| Predicate | contentAuthoringTool |
P11833
|
FINISHED |
| Object | Microsoft Help Workshop |
—
|
NE NERFINISHED |
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: Microsoft Help Workshop | Statement: [Windows Help, contentAuthoringTool, Microsoft Help Workshop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentAuthoringTool Context triple: [Windows Help, contentAuthoringTool, Microsoft Help Workshop]
-
A.
writingTool
chosen
Indicates that one entity serves as a tool or instrument used by another entity for the act of writing.
-
B.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
C.
coCreatedWith
Indicates that an entity participated jointly with another entity in the creation or production of something.
-
D.
coEditor
Indicates that two or more entities share responsibility for editing the same work or publication.
-
E.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 4:19 p.m.