Triple
T4806001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Dragoon Guards |
E106948
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | RDG |
E106948
|
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: RDG | Statement: [Royal Dragoon Guards, abbreviation, RDG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RDG Context triple: [Royal Dragoon Guards, abbreviation, RDG]
-
A.
RDG
RDG is the commonly used abbreviation for the Rail Delivery Group, the industry body representing and coordinating train operators and Network Rail in Great Britain.
-
B.
RDG
chosen
RDG is the abbreviation commonly used for the Royal Dragoon Guards, a cavalry regiment of the British Army.
-
C.
RDG
RDG is the National Rail station code for Reading railway station, a major rail hub in Berkshire, England.
-
D.
Red Devils
Red Devils is the famous nickname of the British 6th Airborne Division, an elite World War II paratroop unit known for its daring airborne operations.
-
E.
Red Devils
Red Devils is the famous nickname of the British 1st Airborne Division, an elite World War II paratroop unit renowned for its daring airborne operations.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6c678e58819094cdf18d8c5ea96f |
completed | March 20, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be440706888190a5f62bef629d3777 |
completed | March 21, 2026, 7:08 a.m. |
Created at: March 20, 2026, 1:23 p.m.