Triple
T20623194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Where Eagles Dare |
E506751
|
entity |
| Predicate | hasObsceneLanguage |
P37187
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Where Eagles Dare, hasObsceneLanguage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObsceneLanguage Context triple: [Where Eagles Dare, hasObsceneLanguage, true]
-
A.
containsProfanity
chosen
Indicates that the referenced content includes one or more profane, vulgar, or offensive expressions.
-
B.
hasPejorativeUsage
Indicates that the referenced term or expression is used in a disparaging, derogatory, or negative manner toward its subject.
-
C.
containsPanegyricsFor
Indicates that one entity includes or features elaborate praise or eulogistic content directed toward another entity.
-
D.
sawMajorOffensive
Indicates that an entity witnessed or experienced a significant, large-scale military or aggressive operation carried out by another entity.
-
E.
usesInclusiveLanguage
Indicates that the subject communicates in a way that avoids biased, exclusionary, or discriminatory language toward any group.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe3177c8190ad1b2ca8b1e0a560 |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:42 a.m.