Triple
T31003847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butler Air Transport |
E790010
|
entity |
| Predicate | passengerOperations |
P53060
|
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: [Butler Air Transport, passengerOperations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerOperations Context triple: [Butler Air Transport, passengerOperations, yes]
-
A.
hasPassengerOperations
chosen
Indicates that an entity conducts or supports transportation services specifically for carrying passengers.
-
B.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
C.
hasPassengerOperator
Indicates that an entity (such as a vehicle or service) is operated by an organization or person responsible for carrying passengers.
-
D.
publicPassengerService
Indicates that an entity provides transportation services that are available to the general public for carrying passengers.
-
E.
passengerSystem
Indicates a relationship where an entity functions as or belongs to a passenger-related system (such as a transport or service system designed for passengers).
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 8:57 p.m.