Triple
T3178293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Time Scale |
E66517
|
entity |
| Predicate | promotionBasis |
P36825
|
FINISHED |
| Object | seniority-cum-fitness |
—
|
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: seniority-cum-fitness | Statement: [Senior Time Scale, promotionBasis, seniority-cum-fitness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionBasis Context triple: [Senior Time Scale, promotionBasis, seniority-cum-fitness]
-
A.
promotionType
Indicates the specific kind or category of promotion associated with an entity or event.
-
B.
promotionReason
chosen
Indicates the reason or justification for which an entity was promoted to a higher position, status, or level.
-
C.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
D.
promotionScope
Indicates the range or extent within which a promotion or promotional offer is valid or applicable.
-
E.
promotionBetween
Indicates a relationship where one entity advances or elevates another entity’s status, rank, or visibility relative to a previous state.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69db2088190baa1305892eb148a |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.