Triple
T23537386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Glaize-Osage Beach Airport |
E577635
|
entity |
| Predicate | publicPrivate |
P8275
|
FINISHED |
| Object | public |
—
|
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: public | Statement: [Grand Glaize-Osage Beach Airport, publicPrivate, public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicPrivate Context triple: [Grand Glaize-Osage Beach Airport, publicPrivate, public]
-
A.
publicOrPrivate
chosen
Indicates whether something is designated as publicly accessible or restricted to private use or access.
-
B.
publicAccess
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
C.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
-
D.
privateParty
Indicates a relationship where an event or gathering is restricted to invited or select participants rather than being open to the public.
-
E.
protectedIn
Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1831688190ac06b84729bce160 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.