Triple
T5608110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PGUM |
E147283
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | PGUM |
E147283
|
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: PGUM | Statement: [PGUM, ICAOCode, PGUM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PGUM Context triple: [PGUM, ICAOCode, PGUM]
-
A.
PGUM
chosen
PGUM is the ICAO airport code for Antonio B. Won Pat International Airport, the primary commercial airport serving Guam.
-
B.
PUM
PUM is the stock ticker symbol for Puma, the German multinational sportswear and athletic footwear company.
-
C.
GUM
GUM is a historic and iconic department store located on Red Square in Moscow, Russia, known for its grand architecture and luxury retail offerings.
-
D.
GUM
GUM is the IATA airport code for Antonio B. Won Pat International Airport, the main commercial airport serving Guam in the western Pacific.
-
E.
PGGM
PGGM is a Dutch pension fund service provider and institutional investor known for its significant investments in sustainable infrastructure and renewable energy projects.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fd1b2c81908da154f7e11b90d8 |
completed | March 22, 2026, 5:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04d4465388190b28f47f11e133b6a |
completed | March 22, 2026, 8:12 p.m. |
Created at: March 22, 2026, 3:39 p.m.