Triple
T25797423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inglourious Basterds (commando unit) |
E649724
|
entity |
| Predicate | allegianceInFiction |
P53264
|
FINISHED |
| Object | Allied forces |
—
|
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: Allied forces | Statement: [Inglourious Basterds (commando unit), allegianceInFiction, Allied forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegianceInFiction Context triple: [Inglourious Basterds (commando unit), allegianceInFiction, Allied forces]
-
A.
alliesInFiction
Indicates that two or more entities are portrayed as allies or cooperative partners within a fictional context or narrative.
-
B.
allegiance
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
C.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
-
D.
allegianceArc
Indicates a change or evolution in an entity’s loyalty or allegiance to another entity over time.
-
E.
hadAllegiance
chosen
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 22, 2026, 6:32 a.m.