Triple
T1844170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-22 Raptor |
E41244
|
entity |
| Predicate | exportRestrictionReason |
P25587
|
FINISHED |
| Object | U.S. federal law prohibition |
—
|
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: U.S. federal law prohibition | Statement: [F-22 Raptor, exportRestrictionReason, U.S. federal law prohibition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportRestrictionReason Context triple: [F-22 Raptor, exportRestrictionReason, U.S. federal law prohibition]
-
A.
protectionReason
Indicates the justification or cause for which protection is provided or required in the relationship between entities.
-
B.
reasonForBan
chosen
Indicates the justification or cause that led to an entity being banned.
-
C.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
D.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
E.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.