Triple
T14484111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBFC |
E359183
|
entity |
| Predicate | issuesRating |
P8710
|
FINISHED |
| Object | PG |
E1024252
|
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: PG | Statement: [BBFC, issuesRating, PG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PG Context triple: [BBFC, issuesRating, PG]
-
A.
PG
PG is the stock ticker symbol for Procter & Gamble, a major American multinational consumer goods company known for brands across household, personal care, and hygiene products.
-
B.
PG
PG is the common abbreviation for Project Gutenberg, a pioneering digital library offering free access to thousands of public-domain ebooks.
-
C.
PG
PG is the IATA airline designator used to identify Bangkok Airways on flight schedules, tickets, and aviation systems.
-
D.
PG
chosen
PG is the ISO 3166 country code for Papua New Guinea, a Pacific nation occupying the eastern half of the island of New Guinea and numerous offshore islands.
-
E.
PG
PG is the international vehicle registration code used for Podgorica, the capital city of Montenegro.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924d7f4c8190b1f62b5ffe1ff649 |
completed | April 14, 2026, 7:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd64a73cf48190811d6de182e891c4 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:20 a.m.