Triple
T18165475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ערבה |
E434880
|
entity |
| Predicate | formsValleySystemWith |
P130709
|
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: [ערבה, formsValleySystemWith, בקעת הירדן]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsValleySystemWith Context triple: [ערבה, formsValleySystemWith, בקעת הירדן]
-
A.
valleyFormed
Indicates that a valley has come into existence or been shaped, typically through geological or erosional processes.
-
B.
valleyType
Indicates the specific kind or classification of a valley that characterizes the relationship between the entities.
-
C.
valleyDesignation
Indicates that an entity is formally designated or classified as a valley in relation to a specified geographic or administrative context.
-
D.
valleyOpensToward
Indicates that a valley is oriented or slopes in the direction of a specified location or feature, effectively opening toward it.
-
E.
valleyLocation
Indicates that one entity is located in, at, or within the geographic bounds of a valley relative to another entity or context.
- 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_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. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:30 a.m.