Triple
T9130400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N334AA |
E219070
|
entity |
| Predicate | hijackedOn |
P34824
|
FINISHED |
| Object | 2001-09-11 |
—
|
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: 2001-09-11 | Statement: [N334AA, hijackedOn, 2001-09-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hijackedOn Context triple: [N334AA, hijackedOn, 2001-09-11]
-
A.
hijacked
Indicates that one entity has forcibly taken control of another entity, typically without authorization and against the will of its rightful controller.
-
B.
hijackingTimeApproximate
chosen
Indicates that the time at which a hijacking occurred is known only approximately rather than as an exact timestamp.
-
C.
pilotHijacker
Indicates that the subject is a pilot who hijacks, or has hijacked, an aircraft.
-
D.
stolenDuring
Indicates that one entity was stolen in the course of, or at the time of, another specified event or time period.
-
E.
numberOfHijackers
Indicates the quantity of individuals who carried out or attempted to carry out a hijacking in the described event or context.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cdafb48190be5e62b15779d771 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.