Triple
T30900496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Speck |
E787150
|
entity |
| Predicate | partnerInDirectingDuo |
P17194
|
FINISHED |
| Object | Josh Gordon |
—
|
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: Josh Gordon | Statement: [Will Speck, partnerInDirectingDuo, Josh Gordon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInDirectingDuo Context triple: [Will Speck, partnerInDirectingDuo, Josh Gordon]
-
A.
partnerInSeries
Indicates that two entities are co-participants or collaborators within the same series, jointly contributing to or appearing in that ongoing sequence.
-
B.
coDirectedWith
chosen
Indicates that two or more entities jointly directed the same work or project.
-
C.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
D.
partnerInActWith
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
-
E.
partnerInProductionCompanyWith
Indicates that two entities are business partners together in operating or owning the same production 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:50 p.m.