Triple
T28904611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | government of Oceania |
E733038
|
entity |
| Predicate | usesSecretPolice |
P87229
|
FINISHED |
| Object | Thought Police |
—
|
NE NERFINISHED |
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: Thought Police | Statement: [government of Oceania, usesSecretPolice, Thought Police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSecretPolice Context triple: [government of Oceania, usesSecretPolice, Thought Police]
-
A.
usedSecretPolice
chosen
Indicates that an entity employed or relied on secret police forces to monitor, control, or repress others.
-
B.
securityAgency
Indicates that one entity functions as a security agency responsible for protection, surveillance, or enforcement activities in relation to another entity.
-
C.
intelligenceAgencyOpposed
Indicates that an intelligence agency actively resists, obstructs, or works against a particular actor, policy, operation, or objective.
-
D.
hasSecretFacility
Indicates that an entity possesses or controls a hidden or undisclosed facility.
-
E.
secretAgencyName
Indicates that an entity is the name or designation of a secret or covert agency associated with another entity.
- 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_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 8:06 a.m.