Triple

T1611251
Position Surface form Disambiguated ID Type / Status
Subject Gist E34617 entity
Predicate protocol P1992 FINISHED
Object Git E34613 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: Git | Statement: [Gist, protocol, Git]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Git
Context triple: [Gist, protocol, Git]
  • A. Git chosen
    Git is a widely used distributed version control system designed to efficiently track changes in source code and support collaborative software development.
  • B. GitHub
    GitHub is a widely used web-based platform for version control and collaborative software development, built around the Git system and popular among open-source and enterprise projects.
  • C. SVN
    SVN is the IATA airport code for Hunter Army Airfield, a U.S. military airfield located near Savannah, Georgia.
  • D. SVN
    SVN is the three-letter ISO 3166-1 alpha-3 country code assigned to Slovenia.
  • E. GitHub Copilot
    GitHub Copilot is an AI-powered code completion and pair-programming tool that suggests code and entire functions directly within developers’ editors.
  • 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa622b9fbc8190bff82acdde10deb6 completed March 6, 2026, 5:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad51c751308190a89f6462ee365418 completed March 8, 2026, 10:39 a.m.
Created at: March 4, 2026, 7:28 p.m.