Triple
T29016568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedosophia |
E737323
|
entity |
| Predicate | coFoundedSPACWith |
P2835
|
FINISHED |
| Object | Social Capital |
—
|
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: Social Capital | Statement: [Hedosophia, coFoundedSPACWith, Social Capital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coFoundedSPACWith Context triple: [Hedosophia, coFoundedSPACWith, Social Capital]
-
A.
coFounderCompany
Indicates that a person is one of the founding members who jointly established a particular company.
-
B.
coFounderWith
chosen
Indicates that two or more entities jointly founded the same organization or venture.
-
C.
coFounderOfFounder
Indicates that one entity is a co-founder of another entity who is themselves a founder of something else.
-
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.
cofounderOf
Indicates that a person jointly established or created an organization, company, or project with one or more other founders.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fe190a081909dabf1e185d1575a |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:46 a.m.