Triple
T22036117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyriatyn |
E544212
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Piryatin |
—
|
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: Piryatin | Statement: [Pyriatyn, hasAlternativeName, Piryatin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piryatin Context triple: [Pyriatyn, hasAlternativeName, Piryatin]
-
A.
Nawalapitiya
Nawalapitiya is a town in Sri Lanka known for its tea plantations and hilly terrain, located within the country's Central Province.
-
B.
Pouni
Pouni is a town in the Reasi district of the Jammu and Kashmir region of India, serving as one of its local commercial and administrative centers.
-
C.
Piro
Piro is a town in the Bhojpur district of Bihar, India, known as one of the district’s principal urban and commercial centers.
-
D.
Piro
Piro is an alternate name for the Yine language, an indigenous Arawakan language spoken in Peru.
-
E.
Pyriatyn
chosen
Pyriatyn is a historic town in central Ukraine, known for its location on the Udai River and its role as a local administrative and cultural center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127f1f95c8190a324c84313cd91ee |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:25 p.m.