Triple
T22615735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | beylerbey |
E558139
|
entity |
| Predicate | wasHighRank |
P58086
|
FINISHED |
| Object | above ordinary provincial governors |
—
|
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 ordinary provincial governors | Statement: [beylerbey, wasHighRank, above ordinary provincial governors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasHighRank Context triple: [beylerbey, wasHighRank, above ordinary provincial governors]
-
A.
isHighRanking
chosen
Indicates that an entity holds a position of relatively great authority, status, or seniority within a hierarchy or organization.
-
B.
wasAbove
Indicates that one entity was positioned at a higher vertical level than another entity at some point in time.
-
C.
highestRanking
Indicates that one entity holds the top or most senior rank relative to a set of other entities.
-
D.
becameHighA
Indicates that an entity transitioned into a state or role characterized as "HighA" (e.g., gaining a higher level, status, or attribute A).
-
E.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167edec2481909c2f06607b3cb8f6 |
completed | April 29, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:59 p.m.