Triple
T38269734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Chaplino |
E1021171
|
entity |
| Predicate | hasAlternativeNameScript |
P63723
|
FINISHED |
| Object | Cyrillic |
—
|
LITERAL FINISHED |
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: Cyrillic | Statement: [New Chaplino, hasAlternativeNameScript, Cyrillic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNameScript Context triple: [New Chaplino, hasAlternativeNameScript, Cyrillic]
-
A.
hasAlternativeNameOfParentLanguage
Indicates that an entity has an alternative or variant name derived from or associated with the name of its parent language.
-
B.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
C.
nativeNameScript
chosen
Indicates the writing system or script in which an entity’s native name is expressed.
-
D.
hasAlternativeToponymy
Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
-
E.
hasNameVariantLanguage
Indicates that a name variant is associated with or expressed in a specific language.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 3, 2026, 4:30 p.m.