Triple
T15919921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seward's Folly |
E386064
|
entity |
| Predicate | hasDerisiveMeaning |
P16869
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Seward's Folly, hasDerisiveMeaning, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerisiveMeaning Context triple: [Seward's Folly, hasDerisiveMeaning, yes]
-
A.
hasIronicMeaning
Indicates that something conveys a meaning opposite to or incongruent with its literal expression, creating an ironic effect.
-
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.
hasMean
Indicates that one entity possesses, exhibits, or is characterized by a particular mean value or average.
-
E.
hasMeaningOfEpithet
Indicates that one entity expresses or conveys the meaning or sense of another entity’s epithet.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.