Triple
T31055565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Остров слёз |
E791385
|
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.
alternateWorkingTitle
Indicates that one title serves as an alternative working title for the same work or project as another title.
-
C.
hasTitleHolderAlternativeName
Indicates that an entity serving as a title holder is known by an alternative or additional name.
-
D.
alternateInterpretationOfTitle
Indicates that one title is an alternative interpretation or reading of another title, reflecting a different way the original title can be understood.
-
E.
hasAlternateTitleRegion
Indicates that an entity has an alternate title that is specifically used or valid within a particular geographic region.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69542e4308190a456d020b37da986 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9 p.m.