Triple
T27162516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zionist settlement of the Negev |
E682697
|
entity |
| Predicate | significantlyExpandedAfter |
P6387
|
FINISHED |
| Object | 1948 Arab–Israeli War |
—
|
NE NERFINISHED |
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: 1948 Arab–Israeli War | Statement: [Zionist settlement of the Negev, significantlyExpandedAfter, 1948 Arab–Israeli War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantlyExpandedAfter Context triple: [Zionist settlement of the Negev, significantlyExpandedAfter, 1948 Arab–Israeli War]
-
A.
significantlyExpandedUnder
Indicates that something grew or increased to a much greater extent during the period or context defined by another entity.
-
B.
wasExpanded
Indicates that something increased in size, scope, or extent compared to its previous state.
-
C.
expandedAfter
chosen
Indicates that one entity increases in size, scope, or extent after another specified event or point in time.
-
D.
wasExpandedIn
Indicates that something increased in size, scope, or extent during a specified time or event.
-
E.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 9:19 a.m.