Triple
T28978998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Transporter |
E734493
|
entity |
| Predicate | ruleOfProtagonist |
P166081
|
FINISHED |
| Object | never change the deal |
—
|
LITERAL FINISHED |
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: never change the deal | Statement: [The Transporter, ruleOfProtagonist, never change the deal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleOfProtagonist Context triple: [The Transporter, ruleOfProtagonist, never change the deal]
-
A.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
B.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
D.
protagonistBasedOn
Indicates that a fictional work’s main character is modeled on, inspired by, or derived from a particular real or fictional person or entity.
-
E.
protagonistMust
Indicates that a particular entity is required to serve as the main character or central focus within a narrative or scenario.
- F. None of above. chosen
Provenance (4 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ee28abc819095e01db1ba054d6f |
completed | May 2, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 9:10 a.m.