Triple
T22940446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrochar Alps |
E569711
|
entity |
| Predicate | accessPoint |
P1985
|
FINISHED |
| Object | Succoth |
—
|
NE NERFINISHED |
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: Succoth | Statement: [Arrochar Alps, accessPoint, Succoth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Succoth Context triple: [Arrochar Alps, accessPoint, Succoth]
-
A.
Succoth
chosen
Succoth is an ancient biblical town east of the Jordan River, mentioned in the Hebrew Bible in connection with the stories of Jacob and Gideon.
-
B.
Mesḥa
Mesḥa is the former name of the modern Israeli town of Kfar Tavor, located in the Lower Galilee region.
-
C.
Ashkelon
Ashkelon is an ancient coastal city in the southern Levant, historically significant as one of the principal cities of the Philistines.
-
D.
Kiryat Ekron
Kiryat Ekron is a small town in central Israel, located near the city of Rehovot and known for its mixed residential and agricultural character.
-
E.
Nitzana
Nitzana is an ancient desert settlement in the Negev region of southern Israel, known for its archaeological remains and historical role on trade and pilgrimage routes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813844b88190b05d3829b0c423c4 |
completed | April 29, 2026, 3:55 a.m. |
Created at: April 17, 2026, 3:45 p.m.