Triple
T26547200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ord. Prof. Dr. |
E671567
|
entity |
| Predicate | denotesSeniority |
P161031
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ord. Prof. Dr., denotesSeniority, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesSeniority Context triple: [Ord. Prof. Dr., denotesSeniority, yes]
-
A.
impliesSeniorityIn
Indicates that one entity is considered to hold a higher rank, status, or level of seniority relative to another entity.
-
B.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
-
C.
hasSeniorityStatus
Indicates that one entity holds a particular level or classification of seniority relative to others.
-
D.
typicalSeniorityLevel
Indicates the usual or most common rank or seniority level associated with an entity in a given context.
-
E.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61436eee08190a23739d9347ec088 |
completed | May 2, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 1:45 a.m.