Triple
T20357966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baba Amr district |
E496699
|
entity |
| Predicate | securityStatusEarly2012 |
P94446
|
FINISHED |
| Object | contested between government and opposition forces |
—
|
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: contested between government and opposition forces | Statement: [Baba Amr district, securityStatusEarly2012, contested between government and opposition forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityStatusEarly2012 Context triple: [Baba Amr district, securityStatusEarly2012, contested between government and opposition forces]
-
A.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
-
B.
securityStatusRange
Indicates the range or interval of possible security status values associated with an entity or context.
-
C.
statusBefore2022
chosen
Indicates that an entity’s status or condition is defined as it existed prior to the year 2022.
-
D.
securityBarrierStatus
Indicates the current operational state or condition of a security barrier (e.g., whether it is active, inactive, open, closed, or otherwise engaged).
-
E.
securedStatus
Indicates that an entity’s state, access, or data has been protected or locked down to prevent unauthorized use or modification.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67855c3a88190b88839a47d01184d |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.