Triple
T11323206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States of India |
E268141
|
entity |
| Predicate | mustActInConformityWith |
P34116
|
FINISHED |
| Object | Fundamental Rights in the Constitution of 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: Fundamental Rights in the Constitution of India | Statement: [States of India, mustActInConformityWith, Fundamental Rights in the Constitution of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustActInConformityWith Context triple: [States of India, mustActInConformityWith, Fundamental Rights in the Constitution of India]
-
A.
decreesMustConformTo
chosen
Indicates that one decree is required to be consistent with, or not contradict, another specified standard, rule, or higher-level decree.
-
B.
mustActIn
Indicates that an entity is required or obligated to perform an action within a specified context, domain, or timeframe.
-
C.
mustRespect
Indicates that one entity is obligated to show respect or deference toward another entity.
-
D.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
-
E.
indicatesComplianceWith
Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e122e48190b3f890de8d561480 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.