Triple
T20396550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossing of the Moselle River |
E500219
|
entity |
| Predicate | defensiveOpposition |
P49607
|
FINISHED |
| Object | prepared German river defenses |
—
|
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: prepared German river defenses | Statement: [Crossing of the Moselle River, defensiveOpposition, prepared German river defenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveOpposition Context triple: [Crossing of the Moselle River, defensiveOpposition, prepared German river defenses]
-
A.
opponentDefensiveLine
chosen
Indicates the defensive line formed by the opposing side in a competitive or adversarial context.
-
B.
defensiveSuccess
Indicates that a defensive action successfully prevented or mitigated an opposing threat, attack, or adverse outcome.
-
C.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
D.
usedDefensiveLine
Indicates that an entity employed or deployed a particular defensive line as part of its strategy or actions.
-
E.
defensiveTactics
Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798b6640819085d5b12dc35633fe |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.