Triple
T35310105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höfle Telegram |
E1019745
|
entity |
| Predicate | listsTimePeriod |
P302
|
FINISHED |
| Object | up to 31 December 1942 |
—
|
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: up to 31 December 1942 | Statement: [Höfle Telegram, listsTimePeriod, up to 31 December 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listsTimePeriod Context triple: [Höfle Telegram, listsTimePeriod, up to 31 December 1942]
-
A.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
B.
periodsGive
Indicates that one period of time provides, yields, or results in something for another period or context.
-
C.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:03 p.m.