Triple
T5536640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Lebanon Army |
E145177
|
entity |
| Predicate | causeOfCollapse |
P694
|
FINISHED |
| Object | Israeli withdrawal from South Lebanon in 2000 |
—
|
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: Israeli withdrawal from South Lebanon in 2000 | Statement: [South Lebanon Army, causeOfCollapse, Israeli withdrawal from South Lebanon in 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfCollapse Context triple: [South Lebanon Army, causeOfCollapse, Israeli withdrawal from South Lebanon in 2000]
-
A.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
B.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
C.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
E.
ceilingCollapseFatalities
Indicates that a ceiling collapse event resulted in one or more fatalities.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fb07e748190bea74bbde2d7b8ba |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.