Triple
T2126668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Service Enterprise Group |
E46441
|
entity |
| Predicate | stockTicker |
P1447
|
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, stockTicker, PEG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEG Context triple: [Public Service Enterprise Group, stockTicker, 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.
Pe
Pe is a Hebrew consonant letter that represents a "p" or "f" sound and has both standard and final written forms.
-
C.
PAL
PAL is the ICAO airline designator for Philippine Airlines, the flag carrier of the Philippines.
-
D.
PB
PB is the post-nominal abbreviation used to denote recipients of the Padma Bhushan, one of India’s highest civilian honors.
-
E.
PE
PE is the two-letter ISO 3166-1 alpha-2 country code assigned to Peru for international standardization and referencing.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb59182081908470f9be97e272c8 |
completed | March 7, 2026, 5:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae51a0e8ac8190992588bf2bf496ab |
completed | March 9, 2026, 4:50 a.m. |
Created at: March 4, 2026, 7:44 p.m.