Triple
T4445129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Operations Command Korea |
E96266
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SOCKOR
SOCKOR is the United States military’s theater special operations command responsible for overseeing and coordinating special operations activities on the Korean Peninsula.
|
E438981
|
NE FINISHED |
How this triple was built (4 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: [Special Operations Command Korea, abbreviation, SOCKOR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SOCKOR Context triple: [Special Operations Command Korea, abbreviation, SOCKOR]
-
A.
SOCC
SOCC is NASA Goddard Space Flight Center’s primary facility for monitoring, controlling, and managing spacecraft operations.
-
B.
SoR
SoR is the commonly used abbreviation for the Society of Rheology, a professional organization dedicated to the study of the flow and deformation of matter.
-
C.
Sokar
Sokar is an ancient Egyptian funerary god associated with the Memphite necropolis, the afterlife, and aspects of death and rebirth.
-
D.
SOU
SOU is the three-letter IATA airport code for Southampton Airport in Hampshire, England.
-
E.
Sozh
The Sozh is a major river in Eastern Europe that flows through Russia, Belarus, and Ukraine before joining the Dnieper.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SOCKOR Triple: [Special Operations Command Korea, abbreviation, SOCKOR]
Generated description
SOCKOR is the United States military’s theater special operations command responsible for overseeing and coordinating special operations activities on the Korean Peninsula.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SOCKOR Target entity description: SOCKOR is the United States military’s theater special operations command responsible for overseeing and coordinating special operations activities on the Korean Peninsula.
-
A.
SOCC
SOCC is NASA Goddard Space Flight Center’s primary facility for monitoring, controlling, and managing spacecraft operations.
-
B.
SoR
SoR is the commonly used abbreviation for the Society of Rheology, a professional organization dedicated to the study of the flow and deformation of matter.
-
C.
Sokar
Sokar is an ancient Egyptian funerary god associated with the Memphite necropolis, the afterlife, and aspects of death and rebirth.
-
D.
SOU
SOU is the three-letter IATA airport code for Southampton Airport in Hampshire, England.
-
E.
Sozh
The Sozh is a major river in Eastern Europe that flows through Russia, Belarus, and Ukraine before joining the Dnieper.
- F. None of above. chosen
Provenance (5 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d00c288190a4f3fec29b5d85b2 |
completed | March 13, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b613850eb88190b689a632b0e2b374 |
completed | March 15, 2026, 2:03 a.m. |
| NEDg | Description generation | batch_69b61464b0dc81909cab007115435b8b |
completed | March 15, 2026, 2:07 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b6151440648190bf8c1c95e20caf13 |
completed | March 15, 2026, 2:10 a.m. |
Created at: March 12, 2026, 11:32 p.m.