Triple
T18168322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Films |
E434952
|
entity |
| Predicate | coFounderRoleOfSamuelJBriskin |
P55842
|
FINISHED |
| Object | executive |
—
|
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: executive | Statement: [Liberty Films, coFounderRoleOfSamuelJBriskin, executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coFounderRoleOfSamuelJBriskin Context triple: [Liberty Films, coFounderRoleOfSamuelJBriskin, executive]
-
A.
cofounderOf
Indicates that a person jointly established or created an organization, company, or project with one or more other founders.
-
B.
coFounderOfFounder
Indicates that one entity is a co-founder of another entity who is themselves a founder of something else.
-
C.
coFounderOccupation
chosen
Indicates that the specified occupation is or was held by a person in their role as a co-founder of an organization.
-
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.
coFounderWith
Indicates that two or more entities jointly founded the same organization or venture.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df52f8b08190ab2c4d76b510cd28 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.