Triple
T14592614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RGS-IBG |
E342480
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | RGS-IBG |
E342480
|
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: RGS-IBG | Statement: [RGS-IBG, shortName, RGS-IBG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RGS-IBG Context triple: [RGS-IBG, shortName, RGS-IBG]
-
A.
RGS-IBG
chosen
RGS-IBG is the United Kingdom’s leading learned society and professional body for geography, promoting geographical research, education, and public understanding of the world.
-
B.
RGS
RGS is the commonly used abbreviation for the Royal Geographical Society, the United Kingdom’s leading learned society and professional body for geography and geographers.
-
C.
BGS
BGS is the United Kingdom’s principal public-sector geoscience research organization, responsible for surveying, monitoring, and providing data on the nation’s geology and related Earth science hazards.
-
D.
BGS
BGS is the National Rail station code assigned to Bogston railway station in Scotland.
-
E.
BGS
BGS is the station code for Berlin-Gesundbrunnen, a major railway and transport hub in Berlin, Germany.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43480d8819084a707e56da2c237 |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda918542c819099646943be59dd04 |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 10, 2026, 1:24 a.m.