Triple
T23008938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intentional Software |
E572853
|
entity |
| Predicate | hasFounderRoleAtMicrosoft |
P127726
|
FINISHED |
| Object | executive |
—
|
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: executive | Statement: [Intentional Software, hasFounderRoleAtMicrosoft, executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderRoleAtMicrosoft Context triple: [Intentional Software, hasFounderRoleAtMicrosoft, executive]
-
A.
roleAtMicrosoft
chosen
Indicates that an entity holds or held a specific role or position within Microsoft.
-
B.
hasNotableRoleOfCoFounder
Indicates that an entity holds a notable role specifically as a co-founder of another entity.
-
C.
hasFoundedCompany
Indicates that a person or entity has established or created a company.
-
D.
workIncludesRoleOfFounder
Indicates that a work involves or credits an entity in the specific role of founder.
-
E.
hasFounderOfDeveloper
Indicates that an entity has as its founder a specific developer who established or created it.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835919b08190ba78e182b87358d4 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.