Triple

T3196531
Position Surface form Disambiguated ID Type / Status
Subject NSFNET E66947 entity
Predicate managedBy P86 FINISHED
Object MCI E41476 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: MCI | Statement: [NSFNET, managedBy, MCI]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MCI
Context triple: [NSFNET, managedBy, MCI]
  • A. MCI
    MCI is a major commercial airport serving the Kansas City metropolitan area in Missouri, United States.
  • B. MCI-Shirley
    MCI-Shirley is a medium- and minimum-security state prison for men located in Shirley, Massachusetts.
  • C. MCI Inc. chosen
    MCI Inc. was a major American telecommunications company and long-distance service provider that played a key role in breaking AT&T’s monopoly before eventually being acquired by Verizon.
  • D. MCA
    MCA is the UK government executive agency responsible for maritime safety, search and rescue coordination, and preventing pollution from ships in UK waters.
  • E. MCA
    MCA was a major American record label and entertainment company known for signing prominent artists and producing a wide range of popular music releases.
  • 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_69ad8588ba18819086a10951c32ecb80 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada7177b488190b7a1b40ff3fae15f completed March 8, 2026, 4:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69b24bb2c9908190b3abc395537e22ac completed March 12, 2026, 5:14 a.m.
Created at: March 8, 2026, 3:07 p.m.