Triple
T18605752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cor |
E454740
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Kor |
—
|
NE NERFINISHED |
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: Kor | Statement: [Cor, hasSpellingVariant, Kor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kor Context triple: [Cor, hasSpellingVariant, Kor]
-
A.
Kor
chosen
Kor is a prominent Klingon warrior and commander from the Star Trek franchise, known as one of the earliest and most iconic Klingon characters in the series.
-
B.
Kuenn
Kuenn is a surname most notably associated with Harvey Kuenn, an American Major League Baseball player and manager.
-
C.
Kol
Kol is a Hebrew surname most notably associated with Moshe Kol, an Israeli politician and one of the signatories of Israel’s Declaration of Independence.
-
D.
KOR
KOR is the ICAO airline designator assigned to Air Koryo, the state-owned national carrier of North Korea.
-
E.
KOR
KOR is the FIFA country code representing the South Korea national football team in international competitions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e547544a248190a3465e22dfb29305 |
completed | April 19, 2026, 9:21 p.m. |
Created at: April 10, 2026, 11:45 a.m.