Triple
T26139622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunhild Line |
E659479
|
entity |
| Predicate | countryInMilitaryContext |
P40676
|
FINISHED |
| Object | Germany |
—
|
NE NERFINISHED |
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: Germany | Statement: [Brunhild Line, countryInMilitaryContext, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryInMilitaryContext Context triple: [Brunhild Line, countryInMilitaryContext, Germany]
-
A.
countryOfUSForces
Indicates that a given country is the nation in which United States military forces are present or operating.
-
B.
countryForWhichFought
Indicates the country on whose behalf or under whose authority an entity participated in a conflict or war.
-
C.
countryControllingOpposingForces
Indicates that a country exercises control or command over military or political forces that are in opposition or conflict with another side.
-
D.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
E.
countryOfMilitaryService
chosen
Indicates that an entity served or is serving in the armed forces of a specified country.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 26, 2026, 8:19 p.m.