Triple
T13058905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenley |
E327649
|
entity |
| Predicate | aerodromeRole |
P66457
|
FINISHED |
| Object | Second World War airfield |
—
|
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: Second World War airfield | Statement: [Kenley, aerodromeRole, Second World War airfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aerodromeRole Context triple: [Kenley, aerodromeRole, Second World War airfield]
-
A.
airfieldRole
chosen
Indicates the functional role or operational purpose that an airfield serves within a broader system or context.
-
B.
airportRole
Indicates that an entity serves a specific functional role or capacity within the context of an airport.
-
C.
airspaceRole
Indicates the specific function or responsibility an entity has within a defined airspace.
-
D.
referredAircraftRole
Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
-
E.
aircraftFacility
Indicates that a facility is designed, equipped, or used to support the operation, maintenance, or accommodation of aircraft.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980e7ee548190b4b18bdb1357c359 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 8:58 p.m.