Triple
T37985124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GO Foundation |
E947666
|
entity |
| Predicate | notableCoFounderRole |
P126416
|
FINISHED |
| Object | Indigenous rights advocate |
—
|
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: Indigenous rights advocate | Statement: [GO Foundation, notableCoFounderRole, Indigenous rights advocate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCoFounderRole Context triple: [GO Foundation, notableCoFounderRole, Indigenous rights advocate]
-
A.
coFounderNotableFor
Indicates that a person is a co-founder of something for which they are notably recognized.
-
B.
notableCoFounderOccupation
chosen
Indicates that the co-founder is particularly notable or recognized for having a specific occupation.
-
C.
hasNotableRoleOfCoFounder
Indicates that an entity holds a notable role specifically as a co-founder of another entity.
-
D.
cofounderOf
Indicates that a person jointly established or created an organization, company, or project with one or more other founders.
-
E.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.