Triple
T17248468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French maintained control of Bergen and secured their position near Frankfurt |
E418687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historicalEventOutcome |
C16784
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historicalEventOutcome Context triple: [French maintained control of Bergen and secured their position near Frankfurt, instanceOf, historicalEventOutcome]
-
A.
historical event aftermath
The historical event aftermath is the period and set of consequences that follow a significant occurrence, encompassing its social, political, economic, and cultural impacts over time.
-
B.
historic event
A historic event is a significant occurrence in the past that has had a lasting impact on societies, cultures, or the course of history.
-
C.
military operation outcome
chosen
A military operation outcome is the overall result or consequence of a planned military action, encompassing its achieved objectives, strategic impact, and associated costs or losses.
-
D.
historical event participant
A historical event participant is an individual, group, or entity that directly or indirectly takes part in, influences, or is affected by a specific historical occurrence.
-
E.
event in ancient history
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
- F. None of above.
Provenance (1 batch)
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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:39 a.m.