Triple
T30579649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamburg cell |
E778346
|
entity |
| Predicate | surveillanceBy |
P1165
|
FINISHED |
| Object | German authorities |
—
|
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: German authorities | Statement: [Hamburg cell, surveillanceBy, German authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveillanceBy Context triple: [Hamburg cell, surveillanceBy, German authorities]
-
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.
observedBy
chosen
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
D.
visibilityControlledBy
Indicates that the visibility or hidden/shown state of one entity is determined or governed by another entity.
-
E.
hasMarketSurveillance
Indicates that an entity performs or is subject to ongoing monitoring and oversight of market activities to detect irregularities or non-compliance.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6894176d0819096fe66b9baab66f1 |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:23 p.m.