Triple
T8416363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airstrip One |
E198738
|
entity |
| Predicate | surveillanceSystem |
P81647
|
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: [Airstrip One, surveillanceSystem, telescreens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveillanceSystem Context triple: [Airstrip One, surveillanceSystem, telescreens]
-
A.
hasCCTV
Indicates that one entity is equipped with or monitored by a CCTV (closed-circuit television) system installed or provided by another entity.
-
B.
sightingSystem
chosen
Indicates a relationship where a system is used to detect, observe, or track targets or objects, typically for monitoring or aiming purposes.
-
C.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
D.
alertSystem
Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
-
E.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c5121081908efa3eca25406d3a |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.