Triple
T29655846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Liquid |
E750260
|
entity |
| Predicate | hasCoCEO |
P202483
|
FINISHED |
| Object | Victor Goossens |
—
|
NE NERFINISHED |
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: Victor Goossens | Statement: [Team Liquid, hasCoCEO, Victor Goossens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoCEO Context triple: [Team Liquid, hasCoCEO, Victor Goossens]
-
A.
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).
-
B.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
C.
hasCoChair
Indicates that an entity shares the role of chair (leadership or oversight position) jointly with another entity.
-
D.
coFounderWasCEOOf
Indicates that a person who co-founded an organization also served as its Chief Executive Officer (CEO) at some point.
-
E.
previousCoCEOWith
Indicates that two entities previously served together as co-chief executive officers of the same organization.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0087de41c48190b2743a26b6d65409 |
completed | May 10, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_6a00870a8bc48190be1385579b8cc1dd |
completed | May 10, 2026, 1:24 p.m. |
| PDg | Predicate description generation | batch_6a0087dd79788190911609d406255be3 |
completed | May 10, 2026, 1:27 p.m. |
Created at: April 28, 2026, 6:55 p.m.