Triple
T32080103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian Flight Information Region |
E819269
|
entity |
| Predicate | surveillanceMeans |
P173519
|
FINISHED |
| Object | primary radar |
—
|
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: primary radar | Statement: [Belgian Flight Information Region, surveillanceMeans, primary radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveillanceMeans Context triple: [Belgian Flight Information Region, surveillanceMeans, primary radar]
-
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.
hasCCTV
Indicates that one entity is equipped with or monitored by a CCTV (closed-circuit television) system installed or provided by another entity.
-
D.
hasSatelliteMonitoring
Indicates that an entity is being observed or tracked using satellite-based monitoring systems.
-
E.
monitorType
Indicates the type or category of monitor associated with or used by an entity.
- F. None of above. chosen
Provenance (4 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b578cef88190bd0ceeeb17a0525f |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:24 a.m.