Triple

T7125157
Position Surface form Disambiguated ID Type / Status
Subject Gauhati High Court E166040 entity
Predicate alsoKnownAs P39 FINISHED
Object GHC E166040 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: GHC | Statement: [Gauhati High Court, alsoKnownAs, GHC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GHC
Context triple: [Gauhati High Court, alsoKnownAs, GHC]
  • A. GHC chosen
    GHC is the Gauhati High Court, the principal judicial authority for the Indian state of Assam and certain neighboring states in the Northeast region.
  • B. GHC
    GHC (Glasgow Haskell Compiler) is the most widely used, feature-rich, and optimizing compiler for the Haskell programming language.
  • C. Haskell
    Haskell is a statically typed, purely functional programming language known for its strong type system, lazy evaluation, and use in both academic research and industry.
  • D. GCH
    GCH is the vehicle registration code assigned to a specific district within Poland’s Pomeranian Voivodeship.
  • E. Yesod
    Yesod is the ninth sefirah in Kabbalistic mysticism, associated with foundation, connection, and the channeling of spiritual energy into the material world.
  • 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_69c6888350588190870cd552b427a1cd completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e64c0f688190a9b7482d86c2f033 completed March 27, 2026, 8:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7a331ff988190886bde89035623c0 completed March 28, 2026, 9:45 a.m.
Created at: March 27, 2026, 2:44 p.m.