Triple
T16311449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo Kahn |
E396064
|
entity |
| Predicate | roleAtStaples |
P122640
|
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: [Leo Kahn, roleAtStaples, co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtStaples Context triple: [Leo Kahn, roleAtStaples, co-founder]
-
A.
roleInProductLine
Indicates the specific functional or organizational role an entity holds within a particular product line.
-
B.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
C.
roleInCUPS
Indicates that an entity holds a specific role or function within the CUPS (Common UNIX Printing System) environment or configuration.
-
D.
roleAtSiebelSystems
Indicates that an entity held a specific role or position at Siebel Systems.
-
E.
productRole
Indicates the functional role or purpose that a product has within a broader system, context, or usage scenario.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288dafb608190be35bd60342bb44e |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.