Triple
T5427988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youniversity Ventures |
E121409
|
entity |
| Predicate | coFounderKevinHartzKnownFor |
P34633
|
FINISHED |
| Object | co-founding Eventbrite |
—
|
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-founding Eventbrite | Statement: [Youniversity Ventures, coFounderKevinHartzKnownFor, co-founding Eventbrite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coFounderKevinHartzKnownFor Context triple: [Youniversity Ventures, coFounderKevinHartzKnownFor, co-founding Eventbrite]
-
A.
cofounderOf
Indicates that a person jointly established or created an organization, company, or project with one or more other founders.
-
B.
founderKnownFor
chosen
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
C.
coFounderOccupation
Indicates that the specified occupation is or was held by a person in their role as a co-founder of an organization.
-
D.
coFounderOfFounder
Indicates that one entity is a co-founder of another entity who is themselves a founder of something else.
-
E.
coFounderCompany
Indicates that a person is one of the founding members who jointly established a particular company.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.