Triple
T115676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of India Act 1919 |
E2332
|
entity |
| Predicate | cameIntoForceInYear |
P6161
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [Government of India Act 1919, cameIntoForceInYear, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoForceInYear Context triple: [Government of India Act 1919, cameIntoForceInYear, 1921]
-
A.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
B.
formedInYear
Indicates the year in which an entity was originally established, created, or came into existence.
-
C.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
D.
commissionedYear
Indicates the year in which something (typically a work, project, or item) was formally ordered, authorized, or put into production.
-
E.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a256456d908190b52c937fe6c4343f |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2578329d08190be82e004b8224d2b |
completed | Feb. 28, 2026, 2:48 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.