Triple
T13190567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hastenbeck |
E313972
|
entity |
| Predicate | countryAftermath |
P88267
|
FINISHED |
| Object | occupation of Hanover by France in 1757 |
—
|
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: occupation of Hanover by France in 1757 | Statement: [Battle of Hastenbeck, countryAftermath, occupation of Hanover by France in 1757]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryAftermath Context triple: [Battle of Hastenbeck, countryAftermath, occupation of Hanover by France in 1757]
-
A.
countryAfterConflict
chosen
Indicates that one country exists in a post-conflict state or status relative to a specified conflict or warring situation.
-
B.
capitalAftermath
Indicates that one entity is the consequence, result, or follow-up state of another entity’s capital-related event or situation.
-
C.
country1
Indicates that the subject entity is a country (or represents a country) in the given context.
-
D.
aftermathOf
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
E.
countryScope
Indicates that something is limited to, applicable within, or defined at the level of a specific country.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.