Triple
T29994159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgievsky Sjezd |
E761971
|
entity |
| Predicate | leadsFrom |
P168342
|
FINISHED |
| Object | Nizhny Novgorod city center |
—
|
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: Nizhny Novgorod city center | Statement: [Georgievsky Sjezd, leadsFrom, Nizhny Novgorod city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadsFrom Context triple: [Georgievsky Sjezd, leadsFrom, Nizhny Novgorod city center]
-
A.
leads
Indicates having primary responsibility for directing, guiding, or managing another entity or group toward a goal or outcome.
-
B.
leadType
Indicates the specific category or classification of a lead within a lead management or sales context.
-
C.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
D.
coLeads
Indicates that two or more entities jointly share primary leadership responsibility over the same project, organization, or initiative.
-
E.
helpsLead
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791d8ecc8190a51ebe4ebfd25f6c |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:39 p.m.