Triple
T19901262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Lebanon security zone |
E478293
|
entity |
| Predicate | collapseOfAlly |
P126340
|
FINISHED |
| Object | South Lebanon Army 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: South Lebanon Army in 2000 | Statement: [South Lebanon security zone, collapseOfAlly, South Lebanon Army in 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapseOfAlly Context triple: [South Lebanon security zone, collapseOfAlly, South Lebanon Army in 2000]
-
A.
countryOfDefeatedSide
Indicates the country to which the losing or defeated side in a conflict, competition, or confrontation belongs.
-
B.
countrySurrendering
Indicates that one country formally yields to another country’s authority or control, typically ending a conflict or war.
-
C.
consequenceOfCollapse
chosen
Indicates that one event, state, or condition occurs as a direct result of a collapse.
-
D.
downfall
Indicates the process or event by which an entity experiences a significant decline, ruin, or loss of power, status, or success.
-
E.
dynastyDissolutionCause
Indicates the reason or factor that led to the dissolution or end of a dynasty.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65941977081909e2f94724eb2c3c0 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.