Triple
T2467928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoreham-by-Sea airfield |
E55296
|
entity |
| Predicate | terminalBuildingStatus |
P38811
|
FINISHED |
| Object | listed building |
—
|
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: listed building | Statement: [Shoreham-by-Sea airfield, terminalBuildingStatus, listed building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalBuildingStatus Context triple: [Shoreham-by-Sea airfield, terminalBuildingStatus, listed building]
-
A.
hasBuildingStatus
chosen
Indicates the current condition, classification, or operational state assigned to a building.
-
B.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
C.
currentBuilding
Indicates that an entity is located in, associated with, or belongs to the building that is relevant in the current context.
-
D.
trainingStatus
Indicates the current state or phase of an entity within a training or learning process.
-
E.
hasStationBuilding
Indicates that a station is associated with or includes a station building as part of its facilities.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0b3ea308190a6d8499c2a542c50 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.