Triple
T28274906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gus Trikonis |
E712959
|
entity |
| Predicate | notableWorkDirected |
P166250
|
FINISHED |
| Object | The Student Body |
—
|
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: The Student Body | Statement: [Gus Trikonis, notableWorkDirected, The Student Body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkDirected Context triple: [Gus Trikonis, notableWorkDirected, The Student Body]
-
A.
workedAsDirectorFor
Indicates that one entity held the role of director in relation to another entity, such as an organization, project, or production.
-
B.
workOfDirector
Indicates that a creative work (such as a film, play, or show) is directed by a particular director.
-
C.
workOfDirectorKnownFor
chosen
Indicates that a work (such as a film or show) is directed by a person for whom this work is one of their notable or best-known creations.
-
D.
directedIn
Indicates that one entity served as the director of another entity, such as a person directing a film, episode, or similar work.
-
E.
directorOfWorkHeAppearsIn
Indicates that a person serves as the director of a work (such as a film, show, or production) in which he himself appears.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: April 27, 2026, 11:19 p.m.