Triple
T9431828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expa |
E227394
|
entity |
| Predicate | foundedByRole |
P5394
|
FINISHED |
| Object | serial entrepreneur |
—
|
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: serial entrepreneur | Statement: [Expa, foundedByRole, serial entrepreneur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedByRole Context triple: [Expa, foundedByRole, serial entrepreneur]
-
A.
founderRole
Indicates that an entity serves as a founder in relation to another entity, specifying the role or capacity in which they established it.
-
B.
foundingRole
chosen
Indicates the specific role or capacity an entity held in the founding or establishment of another entity.
-
C.
founded by
Indicates that an entity was established or created through the initiative, actions, or leadership of another entity.
-
D.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
E.
foundedByOccupation
Indicates that an entity (such as an organization or institution) was founded by a person or group characterized by a specific occupation or professional role.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e6059bc8190a7e98aef3caabd0b |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.