Triple
T20319359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spilve Airport |
E492166
|
entity |
| Predicate | terminalBuildingUse |
P136614
|
FINISHED |
| Object | aviation museum |
—
|
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: aviation museum | Statement: [Spilve Airport, terminalBuildingUse, aviation museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalBuildingUse Context triple: [Spilve Airport, terminalBuildingUse, aviation museum]
-
A.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
B.
terminusAreaUse
chosen
Indicates how the area of a terminus (such as a station or endpoint facility) is utilized or functionally designated.
-
C.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
D.
locatedInBuildingUsedAs
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
E.
typeOfBuildingSpace
Indicates the specific kind or category of building space that an entity represents or occupies.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778abd14819098a01fd32217fdde |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b23a0788190bf1853ef5b81823f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:20 a.m.