Triple

T7582203
Position Surface form Disambiguated ID Type / Status
Subject PGFD E179513 entity
Predicate hasAbbreviation P43 FINISHED
Object PGFD E179513 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: PGFD | Statement: [PGFD, hasAbbreviation, PGFD]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PGFD
Context triple: [PGFD, hasAbbreviation, PGFD]
  • A. PGFD chosen
    PGFD is the fire and emergency medical services agency serving Prince George’s County, Maryland.
  • B. PGFD/EMS
    PGFD/EMS is the combined fire protection and emergency medical services agency serving Prince George’s County, Maryland.
  • C. PFG
    PFG is the stock ticker symbol for Principal Financial Group, a U.S.-based global financial services and investment management company.
  • D. AGFD
    AGFD is the American Chemical Society’s Division of Agricultural and Food Chemistry, focusing on the chemistry of agriculture, food, and related products.
  • E. FGP
    FGP is the stock ticker symbol for FirstGroup, a leading UK-based transport operator running bus and rail services in the United Kingdom and North America.
  • 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_69c69f327db881909a21ae3b156f8ded completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c6f978341081909e009c410ffc5039 completed March 27, 2026, 9:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8617b8934819094f596e6a037e468 completed March 28, 2026, 11:17 p.m.
Created at: March 27, 2026, 3:52 p.m.