Triple
T1410560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombay Time |
E31792
|
entity |
| Predicate | replacedByPolicy |
P3140
|
FINISHED |
| Object | unified national time across 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: unified national time across India | Statement: [Bombay Time, replacedByPolicy, unified national time across India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByPolicy Context triple: [Bombay Time, replacedByPolicy, unified national time across India]
-
A.
replacedPolicyApproach
chosen
Indicates that one policy approach has been superseded and taken the place of another policy approach.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
D.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
E.
conversionPolicyImposedBy
Indicates that a specific conversion policy is mandated or enforced by a particular authority or entity.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e0bfd08190a50820bc7585c28f |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.