Triple
T23675629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сорочинці |
E584864
|
entity |
| Predicate | альтернативнаНазва |
P110696
|
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.
haveAlternativeTitle
chosen
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
B.
trailAlternativeName
Indicates that an entity (such as a trail) is known by an alternative or secondary name.
-
C.
alternateWorkingTitle
Indicates that one title serves as an alternative working title for the same work or project as another title.
-
D.
alternateDescription
Indicates that an entity has an additional or substitute textual description that can be used in place of its primary description.
-
E.
alternateDesignation
Indicates that one entity serves as an alternative name, label, or identifier for another entity.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f2e35c8190ada29694e2cbed37 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.