Triple
T4884274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Lebanon |
E109401
|
entity |
| Predicate | postConflictIssue |
P41238
|
FINISHED |
| Object | land mines and unexploded ordnance |
—
|
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: land mines and unexploded ordnance | Statement: [Southern Lebanon, postConflictIssue, land mines and unexploded ordnance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postConflictIssue Context triple: [Southern Lebanon, postConflictIssue, land mines and unexploded ordnance]
-
A.
postConflictStatus
Indicates the condition or circumstances of an entity after a conflict or dispute has concluded.
-
B.
postConflictContext
chosen
Indicates that the relationship or action occurs within, or is shaped by, a setting that follows the end of an armed conflict or violent confrontation.
-
C.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
D.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
E.
addressedConflictWith
Indicates that one entity has taken action to confront, manage, or resolve a conflict involving another entity.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6de253ac8190b1112da6953fa4f2 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.