Triple
T629213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endeavor Air |
E15887
|
entity |
| Predicate | safetyRegulation |
P14058
|
FINISHED |
| Object | Part 121 air carrier operations |
—
|
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: Part 121 air carrier operations | Statement: [Endeavor Air, safetyRegulation, Part 121 air carrier operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyRegulation Context triple: [Endeavor Air, safetyRegulation, Part 121 air carrier operations]
-
A.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
-
B.
worksOnRegulationType
Indicates that an entity is involved in work or activities related to a specific type or category of regulation.
-
C.
environmentalRegulation
Indicates that one entity imposes rules, standards, or restrictions on another entity’s activities to protect or manage the natural environment.
-
D.
legalRequirement
Indicates that one entity is obligated by law to perform, provide, or comply with something in relation to another entity or situation.
-
E.
regulatoryType
chosen
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e5b5a308190a62165f9275e2f5f |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.