Triple
T28615312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server and Client Access License |
E724259
|
entity |
| Predicate | usedByVendor |
P178295
|
FINISHED |
| Object | Microsoft |
—
|
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 | Statement: [Server and Client Access License, usedByVendor, Microsoft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByVendor Context triple: [Server and Client Access License, usedByVendor, Microsoft]
-
A.
usedByManufacturer
Indicates that a manufacturer makes use of a particular resource, component, method, or tool in its production or operational processes.
-
B.
usesHardwareVendor
Indicates that one entity relies on or employs the hardware products or services provided by a specific hardware vendor.
-
C.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
-
D.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
E.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 28, 2026, 4:31 a.m.