Triple
T82146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft |
E1649
|
entity |
| Predicate | roleOfBillGates |
P268
|
FINISHED |
| Object | Co-founder |
—
|
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: Co-founder | Statement: [Microsoft, roleOfBillGates, Co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfBillGates Context triple: [Microsoft, roleOfBillGates, Co-founder]
-
A.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
B.
hasEconomicRole
Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
-
C.
receivedTuringAwardWith
Indicates that two or more entities jointly received the Turing Award in the same year or for the same recognized contribution.
-
D.
keyPerson
Indicates that a person plays a primary, central, or critically important role in relation to an organization, project, or entity.
-
E.
hasChiefExecutiveRole
Indicates that an entity holds the highest executive leadership position and overall managerial authority within an 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25053ca208190a371b0d38000c2b9 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb2998c819082681da74601d446 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.