Triple
T101446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian English |
E2047
|
entity |
| Predicate | hasNonStandardForm |
P6388
|
FINISHED |
| Object | colloquial Indian English |
—
|
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: colloquial Indian English | Statement: [Indian English, hasNonStandardForm, colloquial Indian English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonStandardForm Context triple: [Indian English, hasNonStandardForm, colloquial Indian English]
-
A.
hasFullForm
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
-
B.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
C.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
D.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
E.
hasStandardizationBody
Indicates that an entity is associated with, governed by, or defined by a specific standards-setting organization or authority.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2563921f8819087f720b1c803579f |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575d8a648190ad8e10d4b04e5e07 |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.