Triple
T28790063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossville Memorial-Whitson Field |
E726925
|
entity |
| Predicate | hasMemorialStatus |
P191790
|
FINISHED |
| Object | memorial airport |
—
|
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: memorial airport | Statement: [Crossville Memorial-Whitson Field, hasMemorialStatus, memorial airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorialStatus Context triple: [Crossville Memorial-Whitson Field, hasMemorialStatus, memorial airport]
-
A.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
B.
hasMemorialContext
Indicates that something is related to, associated with, or situated within the context of a memorial or commemorative setting.
-
C.
hasAdjacentMemorial
Indicates that one memorial is located directly next to or in close proximity to another memorial.
-
D.
hasMemorialElements
Indicates that something includes or incorporates components that serve as a memorial or commemoration of someone or something.
-
E.
hasMemorialPractice
Indicates that an entity engages in or is associated with a particular practice, ritual, or activity intended to commemorate or remember someone or something.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: April 28, 2026, 6:23 a.m.