Triple
T28376982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grizzly Peak Airfield |
E718778
|
entity |
| Predicate | hasTransportationTheme |
P87177
|
FINISHED |
| Object | aviation |
—
|
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 | Statement: [Grizzly Peak Airfield, hasTransportationTheme, aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportationTheme Context triple: [Grizzly Peak Airfield, hasTransportationTheme, aviation]
-
A.
transportTheme
Indicates that an agent or instrument moves or carries a theme (entity) from one place or state to another.
-
B.
hasTransportationElement
chosen
Indicates that one entity includes, involves, or is associated with a specific transportation-related component or feature.
-
C.
hasTransportationSystem
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
-
D.
hasTransportationEvent
Indicates that an entity is involved in or associated with a specific transportation-related occurrence, such as a trip, transfer, or movement event.
-
E.
hasThemePark
Indicates that one entity owns, contains, or is associated with a theme park as part of its properties or offerings.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 28, 2026, 1:03 a.m.