Triple
T28904474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceania (Nineteen Eighty-Four) |
E733035
|
entity |
| Predicate | surveillanceMethod |
P47354
|
FINISHED |
| Object | telescreens |
—
|
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: telescreens | Statement: [Oceania (Nineteen Eighty-Four), surveillanceMethod, telescreens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveillanceMethod Context triple: [Oceania (Nineteen Eighty-Four), surveillanceMethod, telescreens]
-
A.
surveillanceCondition
Indicates the specific circumstances or criteria under which surveillance or monitoring of an entity is required, active, or applicable.
-
B.
surveillanceStrengthenedDuring
Indicates that surveillance measures were intensified or reinforced during a specified time period or event.
-
C.
scrutinyMethods
Indicates the methods or procedures used to examine, inspect, or critically evaluate something.
-
D.
hasObservationMethod
chosen
Indicates that a particular method, technique, or procedure is used to perform or obtain an observation.
-
E.
monitoringApproach
Indicates the method or strategy used to observe, track, or assess a process, condition, or entity over time.
- 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_69f65ad948748190abe57197575a19dc |
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:05 a.m.