Triple
T2767264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Courts of India |
E61365
|
entity |
| Predicate | hasContemptPower |
P544
|
FINISHED |
| Object | power to punish for contempt of court |
—
|
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: power to punish for contempt of court | Statement: [High Courts of India, hasContemptPower, power to punish for contempt of court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContemptPower Context triple: [High Courts of India, hasContemptPower, power to punish for contempt of court]
-
A.
hasPower
chosen
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
C.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
D.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
E.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
- 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_69ab4b7bab6c8190a5c2efef19a8ef34 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfc5e1c8190a5ac2c48d3eaeb0a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.