Triple
T14171476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-18 |
E351216
|
entity |
| Predicate | promotionCriteriaInclude |
P43222
|
FINISHED |
| Object | performance evaluation |
—
|
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: performance evaluation | Statement: [BPS-18, promotionCriteriaInclude, performance evaluation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionCriteriaInclude Context triple: [BPS-18, promotionCriteriaInclude, performance evaluation]
-
A.
evaluationCriteriaInclude
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
B.
legalCriteriaInclude
Indicates that certain legal criteria are contained within, or form part of, a broader set of legal requirements or conditions.
-
C.
promotionDeterminedBy
Indicates that the occurrence or outcome of a promotion is decided or influenced by a specified factor or condition.
-
D.
promotionConditions
chosen
Indicates the conditions or criteria that must be met for a promotion to occur between entities.
-
E.
listingCriterion
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b5dcbc8190b0cfcce5e6c6d582 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:01 a.m.