Triple
T21339481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabrze |
E526141
|
entity |
| Predicate | historicalPeriodOfNameHindenburg |
P39753
|
FINISHED |
| Object | 1915–1945 |
—
|
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: 1915–1945 | Statement: [Zabrze, historicalPeriodOfNameHindenburg, 1915–1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfNameHindenburg Context triple: [Zabrze, historicalPeriodOfNameHindenburg, 1915–1945]
-
A.
dateFormedUnderHindenburg
Indicates that an entity was established or came into existence during the period of Hindenburg’s leadership or authority.
-
B.
historicalEraOfNaming
chosen
Indicates the historical era or time period during which an entity received its name.
-
C.
historicalNameInEnglish
Indicates that an entity is associated with a historical English-language name by which it was known in the past.
-
D.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
E.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a84ce554819090c168c95a5b91f9 |
completed | April 22, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:44 p.m.