Triple
T30860917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorient (encircled and isolated) |
E786058
|
entity |
| Predicate | tacticUsedByGermans |
P30685
|
FINISHED |
| Object | fortified defense |
—
|
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: fortified defense | Statement: [Lorient (encircled and isolated), tacticUsedByGermans, fortified defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticUsedByGermans Context triple: [Lorient (encircled and isolated), tacticUsedByGermans, fortified defense]
-
A.
strategyUsedByGermany
Indicates that a particular strategy is one that was employed or adopted by Germany.
-
B.
aimOfGermanForces
Indicates that the specified objective or target is the intended goal or purpose of the actions undertaken by German military forces.
-
C.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
D.
GermanAircraftUsed
Indicates that an aircraft was used or operated by German forces or organizations.
-
E.
GermanLoss
Indicates that Germany experiences a loss, defeat, or negative outcome in the specified context or event.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:47 p.m.