Triple
T25797425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inglourious Basterds (commando unit) |
E649724
|
entity |
| Predicate | commanderInFiction |
P1061
|
FINISHED |
| Object | Aldo Raine |
—
|
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: Aldo Raine | Statement: [Inglourious Basterds (commando unit), commanderInFiction, Aldo Raine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderInFiction Context triple: [Inglourious Basterds (commando unit), commanderInFiction, Aldo Raine]
-
A.
hasFictionalLeader
Indicates that an entity is led or governed by a leader who is a fictional character rather than a real person.
-
B.
commander
chosen
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
C.
commanderDuringWorldWarII
Indicates that one entity served as a commander of the other specifically during the period of World War II.
-
D.
RepublicanCommander
Indicates that an individual serves as a military commander for the Republican side in a conflict.
-
E.
commanderOfVictoriousSide
Indicates that one entity served as the commanding leader of the side that achieved victory in a conflict or competition relative to 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 6:32 a.m.