Triple
T6438275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tail-Gunner Joe |
E129953
|
entity |
| Predicate | hasDerogatoryConnotation |
P16869
|
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: [Tail-Gunner Joe, hasDerogatoryConnotation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerogatoryConnotation Context triple: [Tail-Gunner Joe, hasDerogatoryConnotation, true]
-
A.
hasConnotation
Indicates that one entity carries an implied or associated meaning, tone, or emotional nuance in relation to another entity.
-
B.
hasPejorativeOrigin
chosen
Indicates that the referenced term, label, or expression originates from a disparaging, derogatory, or contemptuous usage or context.
-
C.
derogatesFrom
Indicates that one entity diminishes, belittles, or detracts from the value, reputation, or importance of another entity.
-
D.
honorificConnotation
Indicates that one entity refers to or characterizes another using an honorific or respectful form, conveying deference or elevated social status.
-
E.
negativeType
Indicates that one entity is classified as a negative, undesirable, or disfavored type in relation to another or within a given context.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06965a5d48190a5860da9e22dc6e0 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:45 p.m.