Triple
T1482174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grab |
E30981
|
entity |
| Predicate | Anthony TanRole |
P21609
|
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: [Grab, Anthony TanRole, co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Anthony TanRole Context triple: [Grab, Anthony TanRole, co-founder]
-
A.
formerDirector
Indicates that one entity previously held the position of director of the other entity but no longer does.
-
B.
foundingDirector
chosen
Indicates that one entity is the original director who established or helped establish the other entity (such as an organization, project, or institution).
-
C.
hasChiefExecutiveRole
Indicates that an entity holds the highest executive leadership position and overall managerial authority within an organization.
-
D.
advisoryCouncilChairedBy
Indicates that an advisory council is led or presided over by a specified chairperson or chairing entity.
-
E.
appointedAs
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6782f088190930d25a56161e2b3 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.