Triple
T36440959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run for the Sun |
E897725
|
entity |
| Predicate | hasVillainBackground |
P194442
|
FINISHED |
| Object | Nazi war criminals |
—
|
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: Nazi war criminals | Statement: [Run for the Sun, hasVillainBackground, Nazi war criminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillainBackground Context triple: [Run for the Sun, hasVillainBackground, Nazi war criminals]
-
A.
hasVillain
Indicates that one entity is the villain or primary antagonist associated with another entity.
-
B.
hasVictimBackground
Indicates that an entity has a background or history of being a victim in a particular context or situation.
-
C.
hasProtagonistBackground
Indicates that a work or narrative features a specified background or origin story for its main protagonist.
-
D.
hasVillainBaseLocation
Indicates that a villain’s primary base or headquarters is located at a specified place.
-
E.
isTypeOfVillain
Indicates that one entity is classified as a particular type or category of villain in relation to another entity.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 3, 2026, 4:10 p.m.