Triple
T10517618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal Radar Approach Control |
E248073
|
entity |
| Predicate | typicalServiceRadius |
P77122
|
FINISHED |
| Object | approximately 30 to 50 nautical miles |
—
|
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: approximately 30 to 50 nautical miles | Statement: [Terminal Radar Approach Control, typicalServiceRadius, approximately 30 to 50 nautical miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServiceRadius Context triple: [Terminal Radar Approach Control, typicalServiceRadius, approximately 30 to 50 nautical miles]
-
A.
neighborhoodRadius
chosen
Indicates the maximum distance around a reference entity within which other entities are considered to be in its neighborhood.
-
B.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
C.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
D.
nearbyCityServed
Indicates that a city is geographically close enough to another city to be considered within its service or support area.
-
E.
serviceAreaName
Indicates the designated name of the geographic or functional area that a service covers or operates within.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cd0fb8819087de2f9a93bad6e6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.