Triple
T34404119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinai wilderness complex |
E883060
|
entity |
| Predicate | traditionallyTraversedBy |
P199215
|
FINISHED |
| Object | Israelite tribes |
—
|
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: Israelite tribes | Statement: [Sinai wilderness complex, traditionallyTraversedBy, Israelite tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyTraversedBy Context triple: [Sinai wilderness complex, traditionallyTraversedBy, Israelite tribes]
-
A.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
B.
usesTraversal
Indicates that one entity performs or relies on a traversal process or path to interact with, reach, or operate on another entity.
-
C.
crossingUsedBy
Indicates that a particular crossing (such as a road, rail, or pedestrian crossing) is utilized or traversed by a specified user or traffic flow.
-
D.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
E.
navigationTraditionStatus
Indicates the status or condition of a tradition related to navigation practices or customs.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
| PDg | Predicate description generation | batch_69ff263632608190a99beb73608066d8 |
completed | May 9, 2026, 12:19 p.m. |
Created at: May 1, 2026, 1:59 a.m.