Triple
T34783558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bibliotheca Palatina |
E1002738
|
entity |
| Predicate | currentLocationOfGermanSection |
P145498
|
FINISHED |
| Object | Heidelberg University Library |
—
|
NE NERFINISHED |
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: Heidelberg University Library | Statement: [Bibliotheca Palatina, currentLocationOfGermanSection, Heidelberg University Library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLocationOfGermanSection Context triple: [Bibliotheca Palatina, currentLocationOfGermanSection, Heidelberg University Library]
-
A.
coveredSectionsLocation
Indicates the specific location or area where the covered sections are situated or applied.
-
B.
segmentLocation
Indicates the spatial or positional relationship specifying where a particular segment is located within a larger structure or context.
-
C.
locationOfTypeSection
Indicates that a particular location is designated as the section or area associated with a specific type or category.
-
D.
currentlyLocatedAt
chosen
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
E.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: May 3, 2026, 3:59 p.m.