Triple
T1639423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Navy |
E35432
|
entity |
| Predicate | cooperatesWith |
P435
|
FINISHED |
| Object | Swiss Army |
E40711
|
NE 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: Swiss Army | Statement: [Swiss Navy, cooperatesWith, Swiss Army]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Swiss Army Context triple: [Swiss Navy, cooperatesWith, Swiss Army]
-
A.
Swiss Army
chosen
The Swiss Army is Switzerland’s national military force, responsible for the country’s defense and organized primarily as a militia with a small professional core.
-
B.
Speer
Speer is a German surname most famously associated with Albert Speer, the Nazi architect and Minister of Armaments and War Production during World War II.
-
C.
Walther
Walther is a given name and surname of Germanic origin, commonly used in German-speaking countries and occasionally in other parts of Europe.
-
D.
Haynrode
Haynrode is a small village in the German state of Thuringia.
-
E.
Sauer
Sauer is a German surname borne by various notable individuals in fields such as science, politics, and the arts.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90a1c2b148190b6610237d5bede10 |
completed | March 5, 2026, 4:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad58df433c81908d93515864c4bf09 |
completed | March 8, 2026, 11:09 a.m. |
Created at: March 4, 2026, 7:28 p.m.