Triple
T8407891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit of St. Louis Airport |
E198544
|
entity |
| Predicate | hasCharterServices |
P81835
|
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: [Spirit of St. Louis Airport, hasCharterServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharterServices Context triple: [Spirit of St. Louis Airport, hasCharterServices, yes]
-
A.
hasCharter
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
-
B.
hasCharterStatus
Indicates that an entity possesses a specific charter designation or status granted by an authoritative body.
-
C.
hasCharterPurpose
Indicates that an entity’s purpose or mission, as formally defined in its charter or founding document, is the specified objective or activity.
-
D.
hasConstituentServicesIn
Indicates that an entity provides constituent services within a specified geographic or jurisdictional area.
-
E.
charteredIn
Indicates that an organization or entity has been formally established, authorized, or incorporated within a specified jurisdiction or location.
- F. None of above. chosen
Provenance (4 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb8315a8a8819097f6da11b909b527 |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:05 p.m.