Triple
T32080090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian Flight Information Region |
E819269
|
entity |
| Predicate | neighboringFIR |
P17964
|
FINISHED |
| Object | Amsterdam Flight Information Region |
—
|
NE NERFINISHED |
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: Amsterdam Flight Information Region | Statement: [Belgian Flight Information Region, neighboringFIR, Amsterdam Flight Information Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringFIR Context triple: [Belgian Flight Information Region, neighboringFIR, Amsterdam Flight Information Region]
-
A.
neighboringProvision
Indicates that one entity provides resources, services, or support to another entity located nearby or in an adjacent area.
-
B.
neighboringPower
Indicates that one entity is a political or territorial power whose domain directly borders or lies adjacent to that of another entity.
-
C.
neighboringTo
Indicates that one entity is located directly adjacent or very close to another entity, sharing a common boundary or immediate vicinity.
-
D.
neighboringRegion
chosen
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
E.
neighboringPort
Indicates that two ports are geographically close to each other, typically sharing a boundary or lying within a short distance along a coast or waterway.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 12:24 a.m.