Triple
T26547204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ord. Prof. Dr. |
E671567
|
entity |
| Predicate | usedAsTitleOn |
P173685
|
FINISHED |
| Object | academic publications |
—
|
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: academic publications | Statement: [Ord. Prof. Dr., usedAsTitleOn, academic publications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTitleOn Context triple: [Ord. Prof. Dr., usedAsTitleOn, academic publications]
-
A.
usedAsTitleOnReleasesBy
Indicates that a work or phrase is used as the title on releases (such as albums, singles, or other published items) created by a specific artist or entity.
-
B.
usedAsTitleUntil
Indicates that a particular title was held or used by an entity up to (and including or until) a specified end time.
-
C.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
D.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
E.
usedAsMarketingTitleIn
Indicates that something serves as a marketing title or promotional label within a specified context or medium.
- 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_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 27, 2026, 1:45 a.m.