Triple
T35310079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höfle Telegram |
E1019745
|
entity |
| Predicate | sentDuring |
P145697
|
FINISHED |
| Object | World War II |
—
|
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: World War II | Statement: [Höfle Telegram, sentDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentDuring Context triple: [Höfle Telegram, sentDuring, World War II]
-
A.
sentIn
Indicates that something (such as a message, document, or item) was transmitted or dispatched to a recipient or destination at a particular time or via a particular medium.
-
B.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
C.
sentWhen
chosen
Indicates the time or temporal context at which a message, item, or communication was sent.
-
D.
sentAfter
Indicates that one message or item was sent at a later time than another specified message or item.
-
E.
sentOver
Indicates that one entity transmitted or dispatched something to another entity, typically across some distance or medium.
- 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_69f7905415488190bb8114e5373b862f |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.