Triple
T23488581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Police Act 1861 |
E570607
|
entity |
| Predicate | inForceAfterIndependence |
P152571
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Indian Police Act 1861, inForceAfterIndependence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceAfterIndependence Context triple: [Indian Police Act 1861, inForceAfterIndependence, yes]
-
A.
inForceOnIndependenceDate
Indicates that a rule, agreement, or legal provision was already in effect on the specified independence date.
-
B.
gainedIndependenceThrough
Indicates that an entity achieved its independence by means of, or as a result of, a specified process, event, agreement, or struggle.
-
C.
usedAfterIndependenceOf
Indicates that one entity came into use only after the other entity achieved independence.
-
D.
gainedIndependenceAs
Indicates that an entity achieved political or administrative independence in the specific form, status, or identity denoted by another entity.
-
E.
soughtIndependenceFrom
Indicates that one entity actively pursued political or organizational separation and autonomy from another entity.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7d9cc08819084c532b069f867ee |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:04 p.m.