Triple
T26452526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treptow an der Rega |
E665390
|
entity |
| Predicate | historicalOfficialNameLanguage |
P52208
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Treptow an der Rega, historicalOfficialNameLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalOfficialNameLanguage Context triple: [Treptow an der Rega, historicalOfficialNameLanguage, German]
-
A.
languageOfHistoricName
chosen
Indicates the language in which a historic or former name of an entity is expressed.
-
B.
historicalNameInEnglish
Indicates that an entity is associated with a historical English-language name by which it was known in the past.
-
C.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
D.
historicalLanguageOfBearers
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
-
E.
historicalNameInLatin
Indicates that an entity has a historically used name expressed in Latin.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 12:06 a.m.