Triple
T2033478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unternehmen Seelöwe |
E44568
|
entity |
| Predicate | plannedForceType |
P1062
|
FINISHED |
| Object | amphibious assault forces |
—
|
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: amphibious assault forces | Statement: [Unternehmen Seelöwe, plannedForceType, amphibious assault forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedForceType Context triple: [Unternehmen Seelöwe, plannedForceType, amphibious assault forces]
-
A.
forceType
chosen
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
B.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
C.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
D.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
E.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.