Triple
T11494948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 478 |
E272508
|
entity |
| Predicate | statusOfJerusalem |
P99797
|
FINISHED |
| Object | occupied territory |
—
|
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: occupied territory | Statement: [UN Security Council Resolution 478, statusOfJerusalem, occupied territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfJerusalem Context triple: [UN Security Council Resolution 478, statusOfJerusalem, occupied territory]
-
A.
cededJerusalemBy
Indicates a relationship where control or authority over Jerusalem is formally transferred or surrendered by one party to another.
-
B.
positionOnJerusalem
Indicates that one entity occupies or is located at a specific position within the area of Jerusalem.
-
C.
viewOfJerusalem
Indicates that something depicts, presents, or provides a visual representation or perspective of Jerusalem.
-
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.
lostJerusalemTo
Indicates that one party surrendered control of Jerusalem to another, typically through defeat or loss in conflict.
- F. None of above. chosen
Provenance (4 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de183f08190abfa36eaabc61dc6 |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.