Triple
T1960919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethsaida |
E42383
|
entity |
| Predicate | hasNearbyModernCity |
P3883
|
FINISHED |
| Object | Golan Heights area settlements |
—
|
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: Golan Heights area settlements | Statement: [Bethsaida, hasNearbyModernCity, Golan Heights area settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyModernCity Context triple: [Bethsaida, hasNearbyModernCity, Golan Heights area settlements]
-
A.
hasNearbyTown
chosen
Indicates that one location has a town situated close to it in geographic proximity.
-
B.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
C.
passesNearCity
Indicates that the path, route, or trajectory of one entity goes close to, but not necessarily through, a specified city.
-
D.
hasFamousCity
Indicates that an entity possesses or is associated with a city that is widely recognized or renowned.
-
E.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.