Triple
T32524129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COVID-19 pandemic in Belgium |
E831261
|
entity |
| Predicate | borderMeasure |
P198828
|
FINISHED |
| Object | travel restrictions |
—
|
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: travel restrictions | Statement: [COVID-19 pandemic in Belgium, borderMeasure, travel restrictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderMeasure Context triple: [COVID-19 pandemic in Belgium, borderMeasure, travel restrictions]
-
A.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
B.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
C.
borderInternal
Indicates that one entity lies within the interior of another and shares a common boundary with it, without touching the outer boundary of the containing entity.
-
D.
borderSectionLength
Indicates the measured length of a specific segment of a shared border between two geographic or administrative areas.
-
E.
shareBorderLengthApprox
Indicates that two entities share a common boundary whose length is approximately equal to a specified value.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69ff0d800ee88190835e233d9e846cdb |
completed | May 9, 2026, 10:33 a.m. |
Created at: May 1, 2026, 1:01 a.m.