Triple
T26547192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ord. Prof. Dr. |
E671567
|
entity |
| Predicate | usedBeforeNameOf |
P170630
|
FINISHED |
| Object | person with full professorship |
—
|
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: person with full professorship | Statement: [Ord. Prof. Dr., usedBeforeNameOf, person with full professorship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBeforeNameOf Context triple: [Ord. Prof. Dr., usedBeforeNameOf, person with full professorship]
-
A.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
B.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
C.
usedAfterName
Indicates that one element is used or appears immediately after a name in some context or representation.
-
D.
nameUsedBefore
Indicates that a particular name has been used or referenced at an earlier time or in a prior context relative to the current one.
-
E.
currentNameUsedFrom
Indicates that an entity’s currently used name has been in effect starting from a specified point in time or source.
- 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_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 1:45 a.m.