Triple
T35310097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höfle Telegram |
E1019745
|
entity |
| Predicate | listsLocationCode |
P183007
|
FINISHED |
| Object | L (Lublin-Majdanek) |
—
|
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: L (Lublin-Majdanek) | Statement: [Höfle Telegram, listsLocationCode, L (Lublin-Majdanek)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listsLocationCode Context triple: [Höfle Telegram, listsLocationCode, L (Lublin-Majdanek)]
-
A.
locationCode
Indicates the specific coded location associated with an entity, event, or relationship.
-
B.
locationCodeMeaning
Indicates the semantic description or interpretation associated with a specific location code.
-
C.
locationCodePart
Indicates that one location code is a constituent or segment of another, larger location code.
-
D.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
E.
cityLocation
Indicates that a city is geographically situated within or associated with a specific larger area or place.
- F. None of above. chosen
Provenance (4 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.