Triple
T25797433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inglourious Basterds (commando unit) |
E649724
|
entity |
| Predicate | fictionalLanguageContext |
P116831
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Inglourious Basterds (commando unit), fictionalLanguageContext, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalLanguageContext Context triple: [Inglourious Basterds (commando unit), fictionalLanguageContext, English]
-
A.
fictionalLanguage
Indicates a relationship where an entity uses, is expressed in, or is associated with a language that is invented or does not exist in reality.
-
B.
fictionalUniverseLanguage
Indicates that a language is used or exists within a particular fictional universe.
-
C.
languageWithinFiction
chosen
Indicates that a language is used or exists within the context of a fictional work or fictional universe.
-
D.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
-
E.
creativeLanguage
Indicates that an entity uses language in an original, imaginative, or non-literal way to express ideas.
- 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_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 22, 2026, 6:32 a.m.