Triple
T25228028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendon |
E632143
|
entity |
| Predicate | formerAerodrome |
P171382
|
FINISHED |
| Object | Hendon Aerodrome |
—
|
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: Hendon Aerodrome | Statement: [Hendon, formerAerodrome, Hendon Aerodrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAerodrome Context triple: [Hendon, formerAerodrome, Hendon Aerodrome]
-
A.
airfieldAlsoKnownAs
Indicates that an airfield is referred to by an alternative name or alias.
-
B.
airfieldDecommissioned
Indicates that an airfield has been officially taken out of service and is no longer used for regular aviation operations.
-
C.
hasFormerMilitaryAirfield
Indicates that an entity possesses or is associated with an airfield that was previously used for military purposes but is no longer active as such.
-
D.
formerAirportType
Indicates that an entity previously had a specific airport classification or type, but no longer holds that status.
-
E.
replacedAsMainAirportFor
Indicates that one airport has taken over the role of being the primary or main airport serving a particular area from another airport.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 21, 2026, 1:04 p.m.