Triple

T4059726
Position Surface form Disambiguated ID Type / Status
Subject World War II defences E84780 entity
Predicate hasPart P35 FINISHED
Object Gustav Line E33924 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: Gustav Line | Statement: [World War II defences, hasPart, Gustav Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gustav Line
Context triple: [World War II defences, hasPart, Gustav Line]
  • A. Gustav Line chosen
    The Gustav Line was a major German World War II defensive fortification system in central Italy, designed to block the Allied advance toward Rome.
  • B. Volturno Line
    The Volturno Line was a German World War II defensive fortification system in southern Italy, designed to slow the Allied advance after the invasion of the Italian mainland.
  • C. Mareth Line
    The Mareth Line was a heavily fortified French and later Axis defensive line in southern Tunisia that became a key battleground in the North African campaign of World War II.
  • D. Mannerheim Line
    The Mannerheim Line was a major Finnish fortification system on the Karelian Isthmus that played a central defensive role against the Soviet Union during the Winter War.
  • E. Solntsevskaya Line
    The Solntsevskaya Line is a line of the Moscow Metro system serving western and southwestern districts of Moscow with modern rapid transit connections.
  • 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_69aed933bec881909edfa28ebb69c634 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefbd32c0c8190bc575974ccf831b3 completed March 9, 2026, 4:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69b562a98c488190a7e77cd46ff998bc completed March 14, 2026, 1:29 p.m.
Created at: March 9, 2026, 3:38 p.m.