Triple
T18165450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ערבה |
E434880
|
entity |
| Predicate | lowestPointRelative |
P98274
|
FINISHED |
| Object | קרובה לאזור ים המלח |
—
|
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: קרובה לאזור ים המלח | Statement: [ערבה, lowestPointRelative, קרובה לאזור ים המלח]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowestPointRelative Context triple: [ערבה, lowestPointRelative, קרובה לאזור ים המלח]
-
A.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
B.
lowestPointsNear
chosen
Indicates that one entity identifies or specifies the locations of the lowest points in elevation or value in the vicinity of another entity.
-
C.
lowerLocation
Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
-
D.
lowestLatitude
Indicates that one entity has a latitude value that is lower (i.e., farther south) than another entity or than all others in a given set.
-
E.
lowerBoundaryLocation
Indicates the place or region where the lower or bottom boundary of something is situated.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dec71b7881908d123d0cea3adf1f |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.