Triple
T5619435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bottendorf, Thuringia, German Empire |
E147562
|
entity |
| Predicate | historicalLocationOfBirthOf |
P12823
|
FINISHED |
| Object | Johannes Steinhoff |
—
|
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: Johannes Steinhoff | Statement: [Bottendorf, Thuringia, German Empire, historicalLocationOfBirthOf, Johannes Steinhoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLocationOfBirthOf Context triple: [Bottendorf, Thuringia, German Empire, historicalLocationOfBirthOf, Johannes Steinhoff]
-
A.
placeOfBirth
Indicates the location where a person or other entity was born.
-
B.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
-
C.
isBirthplaceRelatedTo
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
-
D.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
E.
hasNotablePersonBornHere
chosen
Indicates that a notable or distinguished person was born at the referenced place.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022108db8819098739510366adee1 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.