Triple
T10589646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Biggin Hill Airport |
E249948
|
entity |
| Predicate | openedAsRAFStation |
P94798
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [London Biggin Hill Airport, openedAsRAFStation, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsRAFStation Context triple: [London Biggin Hill Airport, openedAsRAFStation, 1917]
-
A.
closedAsRAFStation
Indicates that a facility or location ceased operations specifically in its role as a Royal Air Force (RAF) station.
-
B.
openedAsRERStation
Indicates that a station began operation specifically as part of the RER (Réseau Express Régional) network from its opening date.
-
C.
openedAsNameForStation
Indicates that a station was originally opened under a particular name.
-
D.
openedAsElevatedStation
Indicates that a station began operation specifically as an elevated (above-ground, raised) facility rather than at-grade or underground.
-
E.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277a39f08190848f24752cfa4b8f |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.