Triple
T6091364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarium Capital |
E135772
|
entity |
| Predicate | hasFounderNotability |
P34633
|
FINISHED |
| Object | co-founder of PayPal |
—
|
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 of PayPal | Statement: [Clarium Capital, hasFounderNotability, co-founder of PayPal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderNotability Context triple: [Clarium Capital, hasFounderNotability, co-founder of PayPal]
-
A.
hasNotableFounder
Indicates that an entity was founded or established by a person or organization considered especially significant or noteworthy.
-
B.
hasFounderName
Indicates that an entity has a founder whose personal name is given by the associated value.
-
C.
founderKnownFor
chosen
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
D.
hasTypicalFounder
Indicates that an entity is commonly or characteristically founded or established by a particular type of founder.
-
E.
hasFounderOfDeveloper
Indicates that an entity has as its founder a specific developer who established or created it.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057ab7324819086d4708e6f9391c0 |
completed | March 22, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.