Triple
T29178266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie "Neck" Jordan |
E739675
|
entity |
| Predicate | isSupportingCharacterIn |
P7748
|
FINISHED |
| Object | Sabotage (2014 film) |
—
|
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: Sabotage (2014 film) | Statement: [Eddie "Neck" Jordan, isSupportingCharacterIn, Sabotage (2014 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSupportingCharacterIn Context triple: [Eddie "Neck" Jordan, isSupportingCharacterIn, Sabotage (2014 film)]
-
A.
supportingCharacter
chosen
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
B.
supportingCharacterPortrayedBy
Indicates that a supporting (non-leading) character in a work is portrayed or acted by a specific performer.
-
C.
hasFictionalCoStar
Indicates that one entity appears as a co-star alongside another entity within a fictional work or narrative.
-
D.
supportedByCharacter
Indicates that an entity receives backing, assistance, or endorsement from a specific character.
-
E.
hasMainCharacterFrom
Indicates that a work of fiction has a main character who originates from or belongs to a specified place, group, or source.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66341f3c48190b00ea32e69a9c281 |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:56 a.m.