Triple
T24884174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Клязьма |
E622801
|
entity |
| Predicate | связана с городом |
P25162
|
FINISHED |
| Object | Орехово-Зуево |
—
|
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: Орехово-Зуево | Statement: [Клязьма, связана с городом, Орехово-Зуево]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: связана с городом Context triple: [Клязьма, связана с городом, Орехово-Зуево]
-
A.
hasAssociatedCity
chosen
Indicates that one entity is linked or related to a specific city, typically as its location, base, or primary area of association.
-
B.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
C.
linkedCity
Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
-
D.
associatedWithCityFoundation
Indicates a relationship where an entity is connected to, involved in, or relevant to the founding or establishment of a particular city.
-
E.
cityAssociatedWith
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:25 a.m.