Triple
T14695265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-14 |
E345138
|
entity |
| Predicate | hasSeniorityStatus |
P115385
|
FINISHED |
| Object | above lower clerical grades |
—
|
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: above lower clerical grades | Statement: [BPS-14, hasSeniorityStatus, above lower clerical grades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeniorityStatus Context triple: [BPS-14, hasSeniorityStatus, above lower clerical grades]
-
A.
hasPermanentSeniority
Indicates that one entity holds a fixed, enduring precedence or higher rank over another that does not change over time.
-
B.
isTenuredPosition
Indicates that a position is a permanent academic or professional role typically protected from arbitrary dismissal.
-
C.
hasSeniorNCO
Indicates that an entity has, is assigned, or is associated with a senior non-commissioned officer in a supervisory or leadership capacity.
-
D.
hasJuniorStatus
Indicates that one entity holds a lower, subordinate, or less senior status relative to another entity within a defined hierarchy or context.
-
E.
isSeniorTo
Indicates that one entity holds a higher rank, status, or level of authority than another.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58855e081908b38f9515db5677f |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.