Triple

T33666497
Position Surface form Disambiguated ID Type / Status
Subject 15 cm sFH 18/1 (Sf) auf Geschützwagen III/IV (Hummel) E862506 entity
Predicate rearPlacement P49438 FINISHED
Object fighting compartment at rear 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: fighting compartment at rear | Statement: [15 cm sFH 18/1 (Sf) auf Geschützwagen III/IV (Hummel), rearPlacement, fighting compartment at rear]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rearPlacement
Context triple: [15 cm sFH 18/1 (Sf) auf Geschützwagen III/IV (Hummel), rearPlacement, fighting compartment at rear]
  • A. rearIO
    Indicates that one entity is located at or associated with the rear (back) input/output side or interface of another entity.
  • B. locatedBehind chosen
    Indicates that one entity is positioned at the rear of or on the far side of another entity along a given viewing or reference direction.
  • C. rackPosition
    Indicates the spatial placement or slot of an item within a rack or racking system.
  • D. batteryPlacement
    Indicates the spatial or positional relationship specifying where a battery is located or installed relative to another object or system.
  • E. locatedOnFront
    Indicates that one entity is positioned on the front side or face of another entity.
  • 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_69f34984c4008190bb82f33a7819da64 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fa36f640819098051eff7e5a5787 completed May 3, 2026, 7:33 a.m.
PD Predicate disambiguation batch_69f6f96dd4c8819093d6a7bd046a9ad5 completed May 3, 2026, 7:29 a.m.
Created at: May 1, 2026, 1:42 a.m.