Triple
T24340179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravi Shankar Prasad |
E613489
|
entity |
| Predicate | sectorGoverned |
P155771
|
FINISHED |
| Object | law and justice |
—
|
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: law and justice | Statement: [Ravi Shankar Prasad, sectorGoverned, law and justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorGoverned Context triple: [Ravi Shankar Prasad, sectorGoverned, law and justice]
-
A.
sectorOfGovernedEntity
Indicates the economic or administrative sector to which a governed entity (such as a jurisdiction or organization under governance) belongs.
-
B.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
C.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
D.
holderGovernment
Indicates that a government entity serves as the official holder, custodian, or controlling authority over another entity.
-
E.
governingCP
Indicates that one clause or phrase syntactically governs or controls the complementizer phrase (CP) in a sentence.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932461ec8190933bf1e56e0f647e |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:57 a.m.