Triple
T31149359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrey Ivanovich of Serpukhov |
E794026
|
entity |
| Predicate | titleBasedIn |
P196426
|
FINISHED |
| Object | Serpukhov |
—
|
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: Serpukhov | Statement: [Andrey Ivanovich of Serpukhov, titleBasedIn, Serpukhov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleBasedIn Context triple: [Andrey Ivanovich of Serpukhov, titleBasedIn, Serpukhov]
-
A.
titleBasis
Indicates that one entity serves as the basis or source material for the title or name of another entity.
-
B.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
C.
titleDerivedFrom
Indicates that the title of one entity is obtained or adapted from another entity.
-
D.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
E.
title
Indicates that one entity serves as the formal name or designation of another entity.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: April 29, 2026, 9:06 p.m.