Triple
T25797411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inglourious Basterds (commando unit) |
E649724
|
entity |
| Predicate | conflictInFiction |
P1406
|
FINISHED |
| Object | Second World War |
—
|
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: Second World War | Statement: [Inglourious Basterds (commando unit), conflictInFiction, Second World War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictInFiction Context triple: [Inglourious Basterds (commando unit), conflictInFiction, Second World War]
-
A.
storyConflict
Indicates a relationship where a story contains or centers around a central problem, opposition, or tension that drives its plot.
-
B.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
storyConflictSource
Indicates the source or cause from which a story’s central conflict arises.
-
D.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
E.
depictsConflict
Indicates that one entity visually represents or portrays a situation of conflict involving another entity or entities.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffc8635881909f3e05e3903f8d8c |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 6:32 a.m.