Triple
T34129620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khotta Bhasha |
E875387
|
entity |
| Predicate | oftenConsideredAs |
P40551
|
FINISHED |
| Object | form of Khortha |
—
|
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: form of Khortha | Statement: [Khotta Bhasha, oftenConsideredAs, form of Khortha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenConsideredAs Context triple: [Khotta Bhasha, oftenConsideredAs, form of Khortha]
-
A.
alsoConsidered
Indicates that one item is regarded as an alternative or additional option alongside another in a given context.
-
B.
isUnofficiallyRegardedAs
chosen
Indicates that something or someone is commonly or informally considered to have a certain role, status, or identity, without any official recognition or formal designation.
-
C.
culturallyPerceivedAs
Indicates that one entity is regarded or interpreted in a particular way by a culture or cultural group.
-
D.
oftenDepictedAs
Indicates that one entity is frequently represented or portrayed in the form, appearance, or symbolism of another entity.
-
E.
oftenPartOf
Indicates that one entity frequently occurs as a component or subset within another entity, though not necessarily always.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 1:53 a.m.