Triple
T25043089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucky Luke |
E627163
|
entity |
| Predicate | hasNotableAntagonist |
P11706
|
FINISHED |
| Object | Dalton brothers |
—
|
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: Dalton brothers | Statement: [Lucky Luke, hasNotableAntagonist, Dalton brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAntagonist Context triple: [Lucky Luke, hasNotableAntagonist, Dalton brothers]
-
A.
hasAntagonisticProtagonist
Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
-
B.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
C.
hasVillain
Indicates that one entity is the villain or primary antagonist associated with another entity.
-
D.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
E.
notableAdversary
chosen
Indicates that one entity is recognized as a significant or prominent opponent or rival of another 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 18, 2026, 6:08 a.m.