Triple
T13222912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | שכם |
E314799
|
entity |
| Predicate | valleyLocation |
P108600
|
FINISHED |
| Object | between Mount Gerizim and Mount Ebal |
—
|
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: between Mount Gerizim and Mount Ebal | Statement: [שכם, valleyLocation, between Mount Gerizim and Mount Ebal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valleyLocation Context triple: [שכם, valleyLocation, between Mount Gerizim and Mount Ebal]
-
A.
valleyRegion
Indicates that one region is characterized as a valley area within a larger geographic or topographic context.
-
B.
valleyDesignation
Indicates that an entity is formally designated or classified as a valley in relation to a specified geographic or administrative context.
-
C.
valleyKnownFor
Indicates that a particular valley is widely recognized or notable for a specific feature, product, activity, or characteristic.
-
D.
valleyType
Indicates the specific kind or classification of a valley that characterizes the relationship between the entities.
-
E.
valleyUsedFor
Indicates that a valley serves a particular function, purpose, or activity for something or someone.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf74d708190a61d8ad938653b06 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:19 p.m.