Triple
T26027128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | מכתש רמון |
E647323
|
entity |
| Predicate | נמצא בתחומי |
P9687
|
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: [מכתש רמון, נמצא בתחומי, מועצה אזורית רמת הנגב]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: נמצא בתחומי Context triple: [מכתש רמון, נמצא בתחומי, מועצה אזורית רמת הנגב]
-
A.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
B.
foundInRite
Indicates that something (such as an element, object, or action) occurs within, is used in, or is otherwise present as part of a specific rite or ritual.
-
C.
coveredSector
Indicates that one entity provides coverage, service, or operational responsibility for a particular sector or area.
-
D.
foundInParva
Indicates that one entity is contained or located within a smaller subdivision or section (a "parva") of another entity.
-
E.
foundAs
Indicates that one entity is discovered, identified, or observed in the role, form, or state represented by another entity.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605ec65448190895219d85eb0d6a8 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:05 a.m.