Triple
T10780551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INS Hansa |
E254307
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Hansa |
E222952
|
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: Hansa | Statement: [INS Hansa, namedAfter, Hansa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hansa Context triple: [INS Hansa, namedAfter, Hansa]
-
A.
Hansa
chosen
Hansa is a historical term for the Hanseatic League, a powerful medieval commercial and defensive confederation of merchant guilds and market towns in Northern Europe.
-
B.
HMT Leipzig
HMT Leipzig is a renowned German conservatory in Leipzig specializing in music and theatre education, named after composer Felix Mendelssohn Bartholdy.
-
C.
Dukenburg
Dukenburg is a residential district in the southwest of Nijmegen in the Netherlands, known for its post-war urban planning and local railway connectivity.
-
D.
Germaniawerft
Germaniawerft was a major German shipbuilding company and naval shipyard in Kiel, known for constructing warships for the Imperial German Navy and later the Kriegsmarine.
-
E.
Unternehmen Braunschweig
Unternehmen Braunschweig was a German World War II military operation known under the codename "Operation Braunschweig."
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c384bc81908f503f3a2e0503a4 |
completed | April 9, 2026, 5:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de55fbfc70819098eb40cf0d1b9e8c |
completed | April 14, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:17 p.m.