Triple
T25722327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariel |
E645024
|
entity |
| Predicate | legalPositionIsrael |
P89144
|
FINISHED |
| Object | disputes characterization of settlement illegality |
—
|
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: disputes characterization of settlement illegality | Statement: [Ariel, legalPositionIsrael, disputes characterization of settlement illegality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalPositionIsrael Context triple: [Ariel, legalPositionIsrael, disputes characterization of settlement illegality]
-
A.
statusUnderIsraeliLaw
chosen
Indicates the legal standing or classification an entity holds according to Israeli law.
-
B.
regionOnWestBank
Indicates that one region is located on the western bank of another geographic feature, such as a river or body of water.
-
C.
roleInIsrael
Indicates that an entity holds or held a specific role, position, or function within the context of Israel.
-
D.
statusOfJerusalem
Indicates the political or legal condition, control, or recognition of Jerusalem at a given time.
-
E.
positionOnJerusalem
Indicates that one entity occupies or is located at a specific position within the area of Jerusalem.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 21, 2026, 10:04 p.m.