Triple
T8935846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McComb-Pike County Airport |
E212772
|
entity |
| Predicate | serves region |
P30177
|
FINISHED |
| Object | southwestern Mississippi |
—
|
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: southwestern Mississippi | Statement: [McComb-Pike County Airport, serves region, southwestern Mississippi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serves region Context triple: [McComb-Pike County Airport, serves region, southwestern Mississippi]
-
A.
serviceRegion
chosen
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
B.
servesStateCapitalRegion
Indicates that an entity provides services or functions as a service hub for the state capital region.
-
C.
servesProvince
Indicates that one entity (typically an organization, service, or administrative unit) provides service or has jurisdiction over a specified province.
-
D.
regionServedFromHub
Indicates that a particular region receives its services, operations, or logistical support from a specified hub location.
-
E.
formerServesRegion
Indicates that an entity previously served, represented, or had official responsibility for a given region, but no longer does so.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66928cec8190915636d663f843af |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:58 p.m.