Triple
T37098138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uglich Reservoir |
E918621
|
entity |
| Predicate | notableStructureInArea |
P114274
|
FINISHED |
| Object | Kalyazin bell tower |
E2146973
|
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: Kalyazin bell tower | Statement: [Uglich Reservoir, notableStructureInArea, Kalyazin bell tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStructureInArea Context triple: [Uglich Reservoir, notableStructureInArea, Kalyazin bell tower]
-
A.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
B.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
C.
hasFamousStructure
chosen
Indicates that an entity possesses or is associated with a well-known or widely recognized structure.
-
D.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
E.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
- F. None of above.
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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdd2e4a88190b83648ebb7a68b96 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.