Triple
T30244501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | correspondsToModernGermanName |
P20950
|
FINISHED |
| Object | Speyer |
—
|
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: Speyer | Statement: [Spira, correspondsToModernGermanName, Speyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToModernGermanName Context triple: [Spira, correspondsToModernGermanName, Speyer]
-
A.
equivalentSurnameInGerman
Indicates that two surnames are equivalent to each other when translated into or represented in the German language.
-
B.
nameInGerman
Indicates that an entity is known or referred to by a specific name in the German language.
-
C.
correspondsToGermanAbbreviation
Indicates that one entity is the German-language abbreviation or acronym that corresponds to, or represents, the other entity.
-
D.
hasModernName
chosen
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
E.
EuropeanNameVariant
Indicates that one name is a variant or alternative form of another name as used in a European language or cultural context.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 7:39 p.m.