Triple
T30829696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceanside Municipal Airport |
E785176
|
entity |
| Predicate | has primary use |
P125948
|
FINISHED |
| Object | flight training |
—
|
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: flight training | Statement: [Oceanside Municipal Airport, has primary use, flight training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has primary use Context triple: [Oceanside Municipal Airport, has primary use, flight training]
-
A.
isPrimarilyUsedAs
chosen
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
B.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
-
C.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
D.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
E.
laterPrimarilyUsedFor
Indicates that something was initially used for one purpose but, at a later time, came to be used mainly for another specified purpose.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690f8eed08190ae78208498b04506 |
completed | May 3, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.