Triple
T30375121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KRU |
E772663
|
entity |
| Predicate | indicatesRegistrationLocation |
P107132
|
FINISHED |
| Object | district of Günzburg |
—
|
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: district of Günzburg | Statement: [KRU, indicatesRegistrationLocation, district of Günzburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesRegistrationLocation Context triple: [KRU, indicatesRegistrationLocation, district of Günzburg]
-
A.
identifiesRegistrationLocation
chosen
Indicates that an entity specifies the place or jurisdiction where a registration is or should be recorded.
-
B.
implementationLocation
Indicates the place or environment where something is implemented, carried out, or put into effect.
-
C.
definesLocation
Indicates that one entity specifies or establishes the spatial or geographic position of another entity.
-
D.
metadataLocation
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
-
E.
documentationLocation
Indicates the place or resource where relevant documentation for an entity can be found.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68512abec8190bb04dfdf50f7d913 |
completed | May 2, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:59 p.m.