Triple
T6447874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobov |
E139786
|
entity |
| Predicate | hasSplit |
P11294
|
FINISHED |
| Object | Bobov-45 |
E139786
|
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: Bobov-45 | Statement: [Bobov, hasSplit, Bobov-45]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bobov-45 Context triple: [Bobov, hasSplit, Bobov-45]
-
A.
Bobov
chosen
Bobov is a prominent Hasidic dynasty originating in Poland, known for its influential rabbinic leadership, yeshivas, and global Orthodox Jewish community.
-
B.
Bobotov Kuk
Bobotov Kuk is a prominent mountain peak in Montenegro’s Durmitor range, renowned for its dramatic limestone cliffs and panoramic views.
-
C.
Zubov
Zubov is a Russian surname most notably associated with figures such as Hockey Hall of Fame defenseman Sergei Zubov.
-
D.
Borisovich
Borisovich is a common Russian patronymic meaning "son of Boris," used as the middle name in many Russian male full names.
-
E.
Baklanov
Baklanov is a Russian surname most notably associated with Soviet politician and aerospace official Oleg Baklanov.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069afd8c48190b3cab580c813ecab |
completed | March 22, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c65392a6c08190b868fab12260d6c2 |
completed | March 27, 2026, 9:53 a.m. |
Created at: March 22, 2026, 4:47 p.m.