Triple
T21185441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Brien (Nineteen Eighty-Four) |
E522066
|
entity |
| Predicate | pretendsToOppose |
P91484
|
FINISHED |
| Object | Party |
—
|
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: Party | Statement: [O'Brien (Nineteen Eighty-Four), pretendsToOppose, Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pretendsToOppose Context triple: [O'Brien (Nineteen Eighty-Four), pretendsToOppose, Party]
-
A.
secretlyOpposes
chosen
Indicates that one entity is acting against or resisting another entity or its goals without that opposition being openly known or acknowledged.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
hasOppositionalPerception
Indicates that one entity perceives another entity, concept, or situation as being in opposition, conflict, or contradiction to itself or its interests.
-
D.
theoryOpposed
Indicates that one theory stands in opposition to, or conflicts with, another theory.
-
E.
designedToOppose
Indicates that one entity is intentionally created or configured to counteract, resist, or work against another entity or process.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73021671c8190a7b464ece7dbaadd |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:06 p.m.