Triple
T6699903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zarqa River |
E152851
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Jabbok |
E611246
|
NE 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: Jabbok | Statement: [Zarqa River, historicalName, Jabbok]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jabbok Context triple: [Zarqa River, historicalName, Jabbok]
-
A.
Jabbok
chosen
Jabbok is an ancient name, mentioned in the Bible, for the Zarqa River that flows through modern-day Jordan.
-
B.
Samaria stream
Samaria stream is a mountain river running through the Samaria Gorge on the island of Crete, shaping its dramatic landscape and supporting its unique ecosystem.
-
C.
Pishon
Pishon is one of the four rivers mentioned in the biblical Book of Genesis as flowing from the Garden of Eden.
-
D.
Banias River
The Banias River is a major spring-fed stream in the Golan Heights that forms one of the principal headwaters of the Jordan River.
-
E.
Ezion-geber
Ezion-geber was an ancient Red Sea port city mentioned in the Hebrew Bible, serving as a key maritime hub for trade and shipping in the region of Edom.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68807adbc8190b8632df42b39eda0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d0a7355081908a0acfa8d2bb4c09 |
completed | March 27, 2026, 6:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7007f2a648190a10792840536035b |
completed | March 27, 2026, 10:11 p.m. |
Created at: March 27, 2026, 2:05 p.m.