Triple

T5483123
Position Surface form Disambiguated ID Type / Status
Subject GCIE E123512 entity
Predicate relatedTitle P914 FINISHED
Object KCIE E123513 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: KCIE | Statement: [GCIE, relatedTitle, KCIE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KCIE
Context triple: [GCIE, relatedTitle, KCIE]
  • A. KCIE chosen
    KCIE is a post-nominal title signifying a Knight Commander of the Order of the Indian Empire, a former British order of chivalry associated with colonial India.
  • B. KC
    KC is a common shorthand nickname for Kansas City, Missouri, a major Midwestern U.S. city known for its jazz heritage, barbecue, and sports teams.
  • C. KC
    KC is the vehicle registration code used on license plates for the district of Kronach in Upper Franconia, Germany.
  • D. K1
    K1, also known as Masherbrum, is a prominent 7,821-meter peak in the Karakoram range of Pakistan and one of the world’s highest mountains.
  • E. KSJC
    KSJC is the ICAO airport code for Norman Y. Mineta San Jose International Airport, a major commercial airport serving San Jose and California’s Silicon Valley.
  • 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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd925deadc81908e193eeb75b63d90 completed March 20, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf48a4c67081909fb62ddcf0fb3047 completed March 22, 2026, 1:40 a.m.
Created at: March 20, 2026, 2:09 p.m.