Triple
T12722166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Ingolstadt |
E304011
|
entity |
| Predicate | relocationDateToLandshut |
P106567
|
FINISHED |
| Object | 1800 |
—
|
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: 1800 | Statement: [University of Ingolstadt, relocationDateToLandshut, 1800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationDateToLandshut Context triple: [University of Ingolstadt, relocationDateToLandshut, 1800]
-
A.
relocatedToMunichIn
Indicates that an entity moved its location to Munich in a specified year or time period.
-
B.
relocationOpeningDate
Indicates the date on which a relocation (such as a move or transfer to a new place) is officially opened or becomes effective.
-
C.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
D.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
relocationBy
Indicates that one entity causes or performs the movement or transfer of another entity from one location to another.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:24 p.m.