Triple
T3159906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of the Cheesemakers |
E66076
|
entity |
| Predicate | hasTopographicalRole |
P46421
|
FINISHED |
| Object | central ravine of Jerusalem |
—
|
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: central ravine of Jerusalem | Statement: [Valley of the Cheesemakers, hasTopographicalRole, central ravine of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopographicalRole Context triple: [Valley of the Cheesemakers, hasTopographicalRole, central ravine of Jerusalem]
-
A.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
B.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
-
C.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
-
D.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
E.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada61606bc8190a8ad760d680924eb |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:05 p.m.