Triple
T6646778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSG Landers |
E150719
|
entity |
| Predicate | KoreanName |
P17869
|
FINISHED |
| Object | SSG 랜더스 |
E150719
|
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: SSG 랜더스 | Statement: [SSG Landers, KoreanName, SSG 랜더스]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SSG 랜더스 Context triple: [SSG Landers, KoreanName, SSG 랜더스]
-
A.
SSG Landers
chosen
SSG Landers is a professional baseball team in South Korea’s KBO League based in Incheon and owned by Shinsegae Group.
-
B.
Sunwolves
The Sunwolves were a professional Japanese rugby union team that competed in the international Super Rugby competition.
-
C.
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.
-
D.
RDG
RDG is the abbreviation commonly used for the Royal Dragoon Guards, a cavalry regiment of the British Army.
-
E.
RDG
RDG is the National Rail station code for Reading railway station, a major rail hub in Berkshire, England.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b01cecc48190a6d2c26d8d5ab80c |
completed | March 27, 2026, 4:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6eef6def8819084bccdf6f11e63da |
completed | March 27, 2026, 8:56 p.m. |
Created at: March 27, 2026, 2 p.m.