Triple
T28904753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minipax |
E733041
|
entity |
| Predicate | contradictoryNameUsage |
P19186
|
FINISHED |
| Object | Newspeak doublethink |
—
|
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: Newspeak doublethink | Statement: [Minipax, contradictoryNameUsage, Newspeak doublethink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contradictoryNameUsage Context triple: [Minipax, contradictoryNameUsage, Newspeak doublethink]
-
A.
namedForConflict
Indicates that one entity is named after, or in commemoration of, a specific conflict, war, or battle.
-
B.
nameContrastsWith
chosen
Indicates that one name is deliberately chosen or used to highlight a difference or opposition in meaning, style, or identity relative to another name.
-
C.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
D.
nameUsedBefore
Indicates that a particular name has been used or referenced at an earlier time or in a prior context relative to the current one.
-
E.
incorrectInformalUsageOfName
Indicates that one entity uses another entity’s name in an informal context in a way that is considered incorrect or inappropriate.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 28, 2026, 8:06 a.m.