Triple
T22532979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishutan |
E557088
|
entity |
| Predicate | nameInPersianTransliteration |
P75698
|
FINISHED |
| Object | Bishutan |
—
|
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: Bishutan | Statement: [Bishutan, nameInPersianTransliteration, Bishutan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInPersianTransliteration Context triple: [Bishutan, nameInPersianTransliteration, Bishutan]
-
A.
nameInNewPersian
Indicates that an entity’s name is expressed or recorded in the New Persian (modern Persian) language.
-
B.
nameInMiddlePersian
Indicates that an entity is referred to by a particular name when expressed in the Middle Persian language.
-
C.
nameInOldPersian
Indicates that an entity has a specific name as written or known in the Old Persian language.
-
D.
hasPersianName
Indicates that an entity is associated with a name expressed in the Persian language.
-
E.
transliterationName
chosen
Indicates that one entity is the transliterated form of another entity’s name from one writing system into another.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed88cf08190ae7e5b6bf9a80372 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.