Triple
T31785850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Witchford |
E811327
|
entity |
| Predicate | airfieldGridReference |
P172298
|
FINISHED |
| Object | near TL 518 770 |
—
|
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: near TL 518 770 | Statement: [RAF Witchford, airfieldGridReference, near TL 518 770]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airfieldGridReference Context triple: [RAF Witchford, airfieldGridReference, near TL 518 770]
-
A.
airfieldAlsoKnownAs
Indicates that an airfield is referred to by an alternative name or alias.
-
B.
airfieldCode
Indicates that an entity is identified by a specific airfield code used to uniquely reference that airfield.
-
C.
airfieldRole
Indicates the functional role or operational purpose that an airfield serves within a broader system or context.
-
D.
relatedAirfield
Indicates that there is an association or connection between an entity and a specific airfield, such as operational use, location, or administrative linkage.
-
E.
containsAirfield
Indicates that a location or area includes at least one airfield within its boundaries.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe94bac8190982ffcaa73303872 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:37 p.m.