Triple
T38500731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jin |
E919823
|
entity |
| Predicate | workCoDirector |
P398
|
FINISHED |
| Object | Todd Wilderman |
—
|
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: Todd Wilderman | Statement: [Jin, workCoDirector, Todd Wilderman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCoDirector Context triple: [Jin, workCoDirector, Todd Wilderman]
-
A.
workDirector
Indicates that one entity serves as the director (creative or managerial lead) of a particular work or production associated with the other entity.
-
B.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
C.
worksWith
chosen
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.