Triple
T14238221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-19 |
E352941
|
entity |
| Predicate | typicalRoleLevel |
P92411
|
FINISHED |
| Object | high-responsibility leadership positions |
—
|
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: high-responsibility leadership positions | Statement: [BPS-19, typicalRoleLevel, high-responsibility leadership positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoleLevel Context triple: [BPS-19, typicalRoleLevel, high-responsibility leadership positions]
-
A.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typicalExperienceLevel
Indicates the usual or most common level of experience associated with an entity in a given context.
-
C.
typicalSeniorityLevel
chosen
Indicates the usual or most common rank or seniority level associated with an entity in a given context.
-
D.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
E.
approximateRole
Indicates a relationship where one entity serves in a role that is similar to, but not exactly the same as, the specified role for another entity.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62422e28819089e7115052a28c96 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.