Triple
T9829767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCAS Miramar Air Show |
E238752
|
entity |
| Predicate | hasVIPOptions |
P26950
|
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: [MCAS Miramar Air Show, hasVIPOptions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVIPOptions Context triple: [MCAS Miramar Air Show, hasVIPOptions, yes]
-
A.
hasVIPTerminal
Indicates that one entity possesses or provides access to a VIP (very important person) terminal associated with another entity.
-
B.
hasVIPBoxes
chosen
Indicates that an entity provides or contains VIP boxes as part of its facilities or offerings.
-
C.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
D.
hasTransferOption
Indicates that there exists a way or method for something (e.g., funds, data, ownership, or passengers) to be transferred from one entity or location to another.
-
E.
hasOptionsListed
Indicates that one entity presents or enumerates a set of selectable options associated with another entity or context.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3282a2481908913addf2b3fa58b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.