Triple
T25741862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tali–Ihantala memorial |
E648238
|
entity |
| Predicate | hasHistoricalEventTime |
P105686
|
FINISHED |
| Object | Battle of Tali–Ihantala 1944 |
—
|
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: Battle of Tali–Ihantala 1944 | Statement: [Tali–Ihantala memorial, hasHistoricalEventTime, Battle of Tali–Ihantala 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalEventTime Context triple: [Tali–Ihantala memorial, hasHistoricalEventTime, Battle of Tali–Ihantala 1944]
-
A.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
C.
isHistoricNameOfEventAt
Indicates that a given historic name refers to or was used for a specific event that occurred at a particular place or time.
-
D.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
E.
notableEventTime
chosen
Indicates the specific time at which a notable or significant event occurred.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 22, 2026, 3:45 a.m.