Triple
T9120469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Legal Department |
E218833
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | GLD |
E218833
|
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: GLD | Statement: [Government Legal Department, abbreviation, GLD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GLD Context triple: [Government Legal Department, abbreviation, GLD]
-
A.
GLD
chosen
GLD is the abbreviation for the United Kingdom’s Government Legal Department, the principal provider of legal services to central government.
-
B.
GLD
GLD is the National Rail station code for Guildford railway station in Surrey, England.
-
C.
GOLD
GOLD is the radio call sign historically used by the British royal yacht HMY Britannia.
-
D.
Gold
Gold was the codename for one of the five Allied landing beaches used by British forces during the D-Day invasion of Normandy in World War II.
-
E.
Gold
Gold is a chemical element and precious metal highly valued for its rarity, luster, and use in jewelry, currency, and electronics.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a902e08190a7eb4728f32b9e1d |
completed | April 1, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d030867d248190ad5b5ba3047426bb |
completed | April 3, 2026, 9:26 p.m. |
Created at: March 30, 2026, 7:17 p.m.