Triple
T4951719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | #BalDiwas |
E111182
|
entity |
| Predicate | caseSensitiveForm |
P12011
|
FINISHED |
| Object | #BalDiwas |
—
|
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: #BalDiwas | Statement: [#BalDiwas, caseSensitiveForm, #BalDiwas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseSensitiveForm Context triple: [#BalDiwas, caseSensitiveForm, #BalDiwas]
-
A.
caseSensitivityVariant
chosen
Indicates that one string or textual form is a variant of another that differs only in letter casing (e.g., uppercase vs lowercase).
-
B.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
C.
hasCaseInflection
Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language context.
-
D.
hasLowercaseForm
Indicates that one entity is the lowercase version or representation of another entity.
-
E.
centralToCase
Indicates that something plays a pivotal or essential role in determining the outcome or understanding of a particular case.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b6a5d481909ad6f5e0b752496c |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.