Triple
T32183070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLNX |
E822034
|
entity |
| Predicate | associatedWithCompanyCoFounder |
P69206
|
FINISHED |
| Object | Ross Freeman |
E835590
|
NE 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: Ross Freeman | Statement: [XLNX, associatedWithCompanyCoFounder, Ross Freeman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCompanyCoFounder Context triple: [XLNX, associatedWithCompanyCoFounder, Ross Freeman]
-
A.
coFounderCompany
Indicates that a person is one of the founding members who jointly established a particular company.
-
B.
hasCoFounderRoleOf
chosen
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
C.
coFounderWith
Indicates that two or more entities jointly founded the same organization or venture.
-
D.
hasCoFounderRole
Indicates that an entity holds or is assigned the role of co-founder in relation to another entity (such as an organization or project).
-
E.
coFounderAffiliation
Indicates that two or more entities share a co-founding relationship within the same organization or venture.
- F. None of above.
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46c2827c819094e0325854807753 |
completed | June 15, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:34 a.m.