Triple
T24253224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porterville Municipal Airport |
E603590
|
entity |
| Predicate | has activity |
P155339
|
FINISHED |
| Object | flight training |
—
|
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: flight training | Statement: [Porterville Municipal Airport, has activity, flight training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has activity Context triple: [Porterville Municipal Airport, has activity, flight training]
-
A.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
-
C.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
D.
hasPublicActivity
Indicates that an entity engages in actions or behaviors that are visible or accessible to the general public.
-
E.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8bcb1c8190995e464a5f85fba9 |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:05 a.m.