Triple
T22829752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heidelberg University Library |
E565764
|
entity |
| Predicate | subjectAreaFocus |
P96519
|
FINISHED |
| Object | humanities |
—
|
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: humanities | Statement: [Heidelberg University Library, subjectAreaFocus, humanities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectAreaFocus Context triple: [Heidelberg University Library, subjectAreaFocus, humanities]
-
A.
disciplinaryFocus
Indicates the primary academic or professional field, subject area, or discipline that something is centered on or concerned with.
-
B.
regionOfAcademicFocus
Indicates the academic subject area or discipline that an entity (such as a person or program) primarily concentrates on or specializes in.
-
C.
primarySubjectArea
chosen
Indicates the main academic or topical field to which something (such as a work, course, or resource) is most centrally related.
-
D.
subjectAreaLevel
Indicates the hierarchical level or depth of specialization of a particular subject area in relation to others.
-
E.
thematicArea
Indicates the subject or item is associated with, or falls under, a particular thematic area or topic of focus.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2ac8d48190b6dc7edc5ad82bc7 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.