Triple
T30734619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Sobotka |
E782514
|
entity |
| Predicate | cooperatesWithCharacter |
P117209
|
FINISHED |
| Object | Beadie Russell |
—
|
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: Beadie Russell | Statement: [Nick Sobotka, cooperatesWithCharacter, Beadie Russell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperatesWithCharacter Context triple: [Nick Sobotka, cooperatesWithCharacter, Beadie Russell]
-
A.
collaboratesWithCharacter
chosen
Indicates that one character works together with another character toward a shared goal or activity.
-
B.
worksUnderCharacter
Indicates that one character is hierarchically subordinate to another and performs their duties under that character’s authority or supervision.
-
C.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
D.
cooperateThrough
Indicates that entities work together or coordinate their actions by means of a specific intermediary, method, or channel.
-
E.
appliesToCharacter
Indicates that an action, rule, or property is specifically directed toward or relevant for a particular character.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:37 p.m.