Triple
T5409451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu Rashtra |
E120975
|
entity |
| Predicate | notCodifiedAs |
P45839
|
FINISHED |
| Object | official constitutional term in India |
—
|
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: official constitutional term in India | Statement: [Hindu Rashtra, notCodifiedAs, official constitutional term in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notCodifiedAs Context triple: [Hindu Rashtra, notCodifiedAs, official constitutional term in India]
-
A.
notOfficialCodeOf
Indicates that one entity is not the formally recognized or authorized code designation for the other entity.
-
B.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
C.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
-
D.
notDescribedAs
chosen
Indicates that an entity is explicitly not characterized, labeled, or referred to using a particular description or term.
-
E.
notClassifiedAs
Indicates that an entity is explicitly not assigned to, or excluded from, a particular class or category.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8796a420819092c1771407cd1a5d |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.