Triple
T20250949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExpressJet Airlines |
E498552
|
entity |
| Predicate | operatedScheduledPassengerService |
P31751
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ExpressJet Airlines, operatedScheduledPassengerService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedScheduledPassengerService Context triple: [ExpressJet Airlines, operatedScheduledPassengerService, true]
-
A.
operatedPassengerServices
chosen
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
B.
operatesCommuterServiceBetween
Indicates that an entity runs a commuter transportation service connecting two specified locations.
-
C.
operatesTransitSystem
Indicates that one entity manages and runs the public transportation network or services for another entity or area.
-
D.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
E.
hasTimetabledServices
Indicates that scheduled or timetabled services are provided or operate in relation to the referenced 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a79a208190a5a7c0f6515bc393 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.