Triple
T23424851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveillance |
E560764
|
entity |
| Predicate | timeframeOfAction |
P38735
|
FINISHED |
| Object | early 21st century |
—
|
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: early 21st century | Statement: [Surveillance, timeframeOfAction, early 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeOfAction Context triple: [Surveillance, timeframeOfAction, early 21st century]
-
A.
timeframeApproximate
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
-
B.
timeFrameSpecified
chosen
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
C.
frameOfAction
Indicates the contextual situation, setting, or circumstances within which an action or event takes place.
-
D.
timeframeRelative
Indicates a temporal relationship where one event, state, or condition is positioned in time relative to another (e.g., before, after, or overlapping).
-
E.
timeframeOfCrimes
Indicates the period or span of time during which the crimes occurred or were committed.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54951688190a3c5382971af3e41 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.