Triple

T9855148
Position Surface form Disambiguated ID Type / Status
Subject Public Service Enterprise Group Incorporated E239563 entity
Predicate tradedAs P2822 FINISHED
Object PEG E46441 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: PEG | Statement: [Public Service Enterprise Group Incorporated, tradedAs, PEG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PEG
Context triple: [Public Service Enterprise Group Incorporated, tradedAs, PEG]
  • A. PEG chosen
    PEG is the stock ticker symbol for Public Service Enterprise Group, a major U.S. energy company primarily involved in regulated electric and gas utility operations and power generation.
  • B. PEG
    PEG is the IATA airport code for Perugia San Francesco d’Assisi – Umbria International Airport in central Italy.
  • C. PEG
    PEG is a German vehicle registration code assigned to the Bayreuth district region.
  • D. PDG
    PDG is an abbreviation commonly used for the Policy Development Group, an organization focused on formulating and advising on policy matters.
  • E. PGPL
    PGPL is the top professional football league in Iran, featuring the country’s leading clubs in the highest tier of its league system.
  • 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_69ca84e4fdc08190a624425bcef98665 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3960fb481909c90d6d6cafc6222 completed April 2, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1d5f5b6148190bcccebd0aefb4bc9 completed April 5, 2026, 3:24 a.m.
Created at: March 30, 2026, 8:34 p.m.