Triple
T6160180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunni Triangle |
E137419
|
entity |
| Predicate | securityStatusPost2003 |
P11824
|
FINISHED |
| Object | highly unstable |
—
|
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: highly unstable | Statement: [Sunni Triangle, securityStatusPost2003, highly unstable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityStatusPost2003 Context triple: [Sunni Triangle, securityStatusPost2003, highly unstable]
-
A.
securityStatus
chosen
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
-
B.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
C.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
D.
securityOperation
Indicates an action or process carried out to protect, monitor, or defend assets, systems, or environments from threats or unauthorized activities.
-
E.
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.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d3445dc8190822954cee90f0dd7 |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.