Triple
T38100872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel and Golan Heights (pre-1967) |
E951372
|
entity |
| Predicate | statusOfGolanHeights |
P201546
|
FINISHED |
| Object | under Syrian sovereignty |
—
|
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: under Syrian sovereignty | Statement: [Israel and Golan Heights (pre-1967), statusOfGolanHeights, under Syrian sovereignty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfGolanHeights Context triple: [Israel and Golan Heights (pre-1967), statusOfGolanHeights, under Syrian sovereignty]
-
A.
statusOfJerusalem
Indicates the political or legal condition, control, or recognition of Jerusalem at a given time.
-
B.
stateOnWestBank
Indicates that a state is located on the western bank of a specified river or body of water.
-
C.
regionOnWestBank
Indicates that one region is located on the western bank of another geographic feature, such as a river or body of water.
-
D.
cameUnderIsraeliControl
Indicates that one entity transitioned to being governed, occupied, or administered by Israeli authorities.
-
E.
governorateWestBankSide
Indicates that a governorate is located on the West Bank side of a relevant boundary or division.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
| PDg | Predicate description generation | batch_6a00037aff7c8190940bd1b02cec8c57 |
completed | May 10, 2026, 4:03 a.m. |
Created at: May 3, 2026, 4:21 p.m.