Triple
T10382304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Metz |
E244669
|
entity |
| Predicate | campaignCharacteristic |
P49417
|
FINISHED |
| Object | prolonged urban and positional fighting |
—
|
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: prolonged urban and positional fighting | Statement: [Battle of Metz, campaignCharacteristic, prolonged urban and positional fighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignCharacteristic Context triple: [Battle of Metz, campaignCharacteristic, prolonged urban and positional fighting]
-
A.
campaignCharacteristics
chosen
Indicates the defining features, attributes, or qualities that characterize a particular campaign.
-
B.
campaignSymbol
Indicates that something serves as a symbol or emblem representing a particular campaign.
-
C.
policyCharacteristic
Indicates that a policy possesses a particular attribute, feature, or quality that characterizes how it is defined or operates.
-
D.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
E.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e992d8e08190aaa9a04925f52ccc |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.