Triple

T19203839
Position Surface form Disambiguated ID Type / Status
Subject NGC 5408 E480178 entity
Predicate cataloguedIn P1278 FINISHED
Object PGC NE NERFINISHED

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: PGC | Statement: [NGC 5408, cataloguedIn, PGC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PGC
Context triple: [NGC 5408, cataloguedIn, PGC]
  • A. PGC chosen
    PGC is an astronomical catalog that systematically lists and provides data on galaxies, including objects like the Leo II Dwarf Galaxy.
  • B. PGR
    PGR is the stock ticker symbol for The Progressive Corporation, a major U.S. insurance company best known for its auto insurance offerings.
  • C. PGS
    PGS stands for Prompt Global Strike, a U.S. military concept aimed at enabling rapid, precision conventional strikes anywhere in the world within a short time frame.
  • D. PGZ
    PGZ is a major Polish state-owned defense holding company that consolidates much of Poland’s arms and military equipment industry.
  • E. PFG
    PFG is the stock ticker symbol for Principal Financial Group, a U.S.-based global financial services and investment management company.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8cb8c348190b52075823911c869 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5f99b37c081908c13e0b4cca52aa4 completed April 20, 2026, 10:02 a.m.
Created at: April 10, 2026, 1:16 p.m.