Triple
T25259621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ex-Servicemen Contributory Health Scheme |
E633266
|
entity |
| Predicate | adminHeadType |
P165302
|
FINISHED |
| Object | Managing Director, ECHS |
—
|
NE NERFINISHED |
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: Managing Director, ECHS | Statement: [Ex-Servicemen Contributory Health Scheme, adminHeadType, Managing Director, ECHS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminHeadType Context triple: [Ex-Servicemen Contributory Health Scheme, adminHeadType, Managing Director, ECHS]
-
A.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
B.
headdressType
Indicates the specific kind or category of headdress associated with an entity.
-
C.
electHeadBy
Indicates that a group or body selects and appoints a person to serve as its head or leader through an election process.
-
D.
headAttachment
Indicates that one entity is physically or structurally attached to the head or top part of another entity.
-
E.
header
Indicates that one entity serves as a heading or title section that precedes and organizes the content of 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 21, 2026, 1:13 p.m.