Triple
T26027131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | מכתש רמון |
E647323
|
entity |
| Predicate | נוצר כתוצאה מ |
P10791
|
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.
foundedAsResultOf
chosen
Indicates that one entity was established or created as a direct consequence or outcome of another event, action, or circumstance.
-
B.
officeCreatedAsResultOf
Indicates that an office came into existence as a consequence of a specific preceding event, action, or process.
-
C.
involvesCreationOf
Indicates that one entity brings about, produces, or results in the creation of another entity.
-
D.
aftermathOfCreation
Indicates the state, condition, or consequences that exist as a direct result of a prior act of creation.
-
E.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
- 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.