Triple

T17120498
Position Surface form Disambiguated ID Type / Status
Subject Irchel E415450 entity
Predicate hasNearbyArea P4647 FINISHED
Object Oerlikon E877835 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: Oerlikon | Statement: [Irchel, hasNearbyArea, Oerlikon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oerlikon
Context triple: [Irchel, hasNearbyArea, Oerlikon]
  • A. Oerlikon chosen
    Oerlikon is a district in the north of Zurich, Switzerland, known as a major residential, commercial, and transportation hub of the city.
  • B. Oerlikon Contraves
    Oerlikon Contraves is a Swiss defense company renowned for its anti-aircraft and air-defense gun systems used by militaries worldwide.
  • C. Ruhrstahl
    Ruhrstahl was a German armaments manufacturer best known for producing advanced World War II munitions and guided weapons.
  • D. Steyr
    Steyr is a historic industrial city in northern Austria known for its well-preserved old town and long tradition of metalworking and manufacturing.
  • E. Ilster
    The Ilster is a small river in Lower Saxony, Germany, known as one of the headwater streams contributing to the Örtze river system.
  • 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_69d886d090cc8190a39cb94992586905 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3e8092b548190b45c1695be47edc2 completed April 18, 2026, 8:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a013a1062fc8190b1c4e97f42cf3faa completed May 11, 2026, 2:08 a.m.
Created at: April 10, 2026, 5:36 a.m.