Triple
T23523889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan and Israel |
E574580
|
entity |
| Predicate | borderStatusAfter1967 |
P26523
|
FINISHED |
| Object | Israel occupied West Bank from Jordan |
—
|
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: Israel occupied West Bank from Jordan | Statement: [Jordan and Israel, borderStatusAfter1967, Israel occupied West Bank from Jordan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderStatusAfter1967 Context triple: [Jordan and Israel, borderStatusAfter1967, Israel occupied West Bank from Jordan]
-
A.
stateAfter1948
Indicates that an entity holds the status or condition of being a state (or in a particular state) at some point after the year 1948.
-
B.
statusAfter1948
Indicates the status or condition of an entity as it existed after the year 1948.
-
C.
pre1948Status
Indicates the status or condition of an entity as it existed prior to the year 1948.
-
D.
regionOnWestBank
Indicates that one region is located on the western bank of another geographic feature, such as a river or body of water.
-
E.
cameUnderIsraeliControl
chosen
Indicates that one entity transitioned to being governed, occupied, or administered by Israeli authorities.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac71ec8881909bfb706efdc2518f |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.