Triple
T28904619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | government of Oceania |
E733038
|
entity |
| Predicate | enforcesConcept |
P146324
|
FINISHED |
| Object | 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: doublethink | Statement: [government of Oceania, enforcesConcept, doublethink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcesConcept Context triple: [government of Oceania, enforcesConcept, doublethink]
-
A.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
-
B.
supportsConstraint
chosen
Indicates that one entity upholds, enforces, or is compatible with a specified constraint or set of constraints in relation to another entity.
-
C.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
defendsConcept
Indicates that one entity actively supports and argues in favor of a particular concept, idea, or theory, often in response to criticism or challenge.
-
E.
hasImplementedConcept
Indicates that an entity has put a particular concept into practice or realized it in an implemented form.
- 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_69f65ada0060819098ff14053a958b64 |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:06 a.m.