Triple
T36573242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Postal Life Insurance |
E902171
|
entity |
| Predicate | relatedScheme |
P191768
|
FINISHED |
| Object | Rural Postal Life Insurance |
E902171
|
NE 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: Rural Postal Life Insurance | Statement: [Postal Life Insurance, relatedScheme, Rural Postal Life Insurance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedScheme Context triple: [Postal Life Insurance, relatedScheme, Rural Postal Life Insurance]
-
A.
associatedWithScheme
chosen
Indicates that one entity is linked or connected to a particular scheme, framework, or structured plan.
-
B.
relatedGrantScheme
Indicates that there is an associated grant scheme that is relevant or linked to the subject entity.
-
C.
similarSchemeIn
Indicates that one entity uses a scheme or structural pattern that is similar to that used in another entity.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
relatedForm
Indicates that one entity is an alternative or variant form of another, such as a different spelling, inflection, or closely related lexical form.
- F. None of above.
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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f90fee288190a45ee9eb3e0fc78d |
completed | June 23, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.