Triple
T9241270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Airlines Flight 77 |
E222062
|
entity |
| Predicate | securityEventType |
P30019
|
FINISHED |
| Object | aircraft hijacking |
—
|
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: aircraft hijacking | Statement: [American Airlines Flight 77, securityEventType, aircraft hijacking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityEventType Context triple: [American Airlines Flight 77, securityEventType, aircraft hijacking]
-
A.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
B.
hasSecurityEvent
chosen
Indicates that a security-related incident or event is associated with, or has occurred for, a given entity.
-
C.
securityTypeListed
Indicates that a security is officially listed and traded on a recognized exchange or trading venue.
-
D.
securityApparatusRole
Indicates the role or function an entity holds within a security or law-enforcement apparatus.
-
E.
relatedSecurity
Indicates that one security has a defined relationship or association with another security, such as dependency, linkage, or relevance.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cd03ea9d90819096f9ca5321dffd56 |
completed | April 1, 2026, 11:39 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.