Triple
T2989702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Airways Flight 1549 |
E80715
|
entity |
| Predicate | scheduledServiceType |
P44552
|
FINISHED |
| Object | regularly scheduled passenger service |
—
|
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: regularly scheduled passenger service | Statement: [US Airways Flight 1549, scheduledServiceType, regularly scheduled passenger service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledServiceType Context triple: [US Airways Flight 1549, scheduledServiceType, regularly scheduled passenger service]
-
A.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
B.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
-
C.
scheduledInYear
Indicates that an event, activity, or item is planned or set to occur within a specific calendar year.
-
D.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99dcdb00819092ca5f10396408e0 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:59 p.m.