Triple
T16919671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haryana Civil Services |
E410411
|
entity |
| Predicate | typicalEntryPost |
P124721
|
FINISHED |
| Object | HCS (Executive Branch) officer |
—
|
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: HCS (Executive Branch) officer | Statement: [Haryana Civil Services, typicalEntryPost, HCS (Executive Branch) officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntryPost Context triple: [Haryana Civil Services, typicalEntryPost, HCS (Executive Branch) officer]
-
A.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
B.
typicalEntryPhase
Indicates the usual or standard phase at which an entity typically enters into a process, system, or sequence of stages.
-
C.
typicalEntryRoute
Indicates the usual or most common path or method by which something is entered or accessed.
-
D.
typicalArticle
Indicates that one entity is a standard, representative, or commonly occurring instance of the type or category denoted by the other entity.
-
E.
createdPost
Indicates that an entity authored or produced a specific post.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cded2f8481909a20cc08b47e922e |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.