Triple
T30449143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libya–United States relations |
E774660
|
entity |
| Predicate | terrorismDelistingYear |
P92661
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Libya–United States relations, terrorismDelistingYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrorismDelistingYear Context triple: [Libya–United States relations, terrorismDelistingYear, 2006]
-
A.
terrorismDesignationYear
Indicates the year in which an entity was officially designated as involved in terrorism (e.g., as a terrorist organization or supporter).
-
B.
classifiedAsTerroristBy
Indicates that an entity has been designated or labeled as a terrorist by a specified authority, organization, or actor.
-
C.
sanctionYear
Indicates the year in which a sanction was imposed, enacted, or came into effect.
-
D.
removedTerroristDesignation
chosen
Indicates that a prior classification of an entity as a terrorist or terrorist organization has been officially withdrawn or canceled.
-
E.
hasTerroristOrganization
Indicates that an entity is associated with, belongs to, or functions as a terrorist organization.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686c1b7988190a0750c687c5d0dd1 |
completed | May 2, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:09 p.m.