Triple
T18325000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOCKOR |
E438981
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SOCKOR |
—
|
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: SOCKOR | Statement: [SOCKOR, abbreviation, SOCKOR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SOCKOR Context triple: [SOCKOR, abbreviation, SOCKOR]
-
A.
SOCKOR
chosen
SOCKOR is the United States military’s theater special operations command responsible for overseeing and coordinating special operations activities on the Korean Peninsula.
-
B.
SOK
SOK is the abbreviation for the Swedish Olympic Committee, the organization responsible for overseeing Sweden's participation in the Olympic Games.
-
C.
SOK
SOK is the vehicle registration code for the Saale-Orla-Kreis district in the German state of Thuringia.
-
D.
SOK
SOK is the National Rail station code for South Kenton railway station in northwest London.
-
E.
SOKOM
SOKOM is the Danish Special Operations Command, the unified headquarters responsible for overseeing Denmark’s elite special operations forces.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aaa66ac819082ec718e8329e0cc |
completed | April 19, 2026, 5:02 p.m. |
Created at: April 10, 2026, 10:36 a.m.