Triple
T38637878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Imagine |
E937608
|
entity |
| Predicate | softwareOffered |
P89362
|
FINISHED |
| Object | Microsoft Visual Studio |
—
|
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 Visual Studio | Statement: [Microsoft Imagine, softwareOffered, Microsoft Visual Studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareOffered Context triple: [Microsoft Imagine, softwareOffered, Microsoft Visual Studio]
-
A.
offersSoftware
chosen
Indicates that one entity provides or makes software available to another entity.
-
B.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
C.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
D.
associatedOffering
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
-
E.
offersTechnology
Indicates that one entity provides or makes available a technology or technological solution to 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.