Triple
T7834141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erra |
E181647
|
entity |
| Predicate | hasNameInTeluguScript |
P79272
|
FINISHED |
| Object | ఎర్ర |
—
|
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: ఎర్ర | Statement: [Erra, hasNameInTeluguScript, ఎర్ర]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInTeluguScript Context triple: [Erra, hasNameInTeluguScript, ఎర్ర]
-
A.
hasUnicodeName
Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
-
B.
nameInDevanagari
Indicates that an entity’s name is written or represented using the Devanagari script.
-
C.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
-
D.
hasNameInPunjabi
Indicates that an entity is associated with a specific name expressed in the Punjabi language.
-
E.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
- F. None of above. chosen
Provenance (4 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064a47648190af2ca2b336584a92 |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:45 p.m.