Triple
T12079367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morristown Municipal Airport |
E287636
|
entity |
| Predicate | hasCharterOperators |
P63491
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Morristown Municipal Airport, hasCharterOperators, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharterOperators Context triple: [Morristown Municipal Airport, hasCharterOperators, yes]
-
A.
hasCharterServices
Indicates that an entity provides or is associated with charter-based transportation or service offerings for another entity.
-
B.
hasCharter
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
-
C.
hasCharterStatus
Indicates that an entity possesses a specific charter designation or status granted by an authoritative body.
-
D.
supportsCharterFlights
chosen
Indicates that one entity provides the capability or service of operating or accommodating charter flights for another entity.
-
E.
operatedCharterFlights
Indicates that an entity conducted or managed charter flight services for another entity or 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bf4f508190842927e7e0642235 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.