Triple
T32241245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Taejon |
E823618
|
entity |
| Predicate | NKCommander |
P173872
|
FINISHED |
| Object | Choe Hyon |
—
|
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: Choe Hyon | Statement: [Battle of Taejon, NKCommander, Choe Hyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NKCommander Context triple: [Battle of Taejon, NKCommander, Choe Hyon]
-
A.
parallelCommander
Indicates that two or more entities hold equivalent commander roles or authority in parallel, rather than in a strict superior–subordinate hierarchy.
-
B.
cloneCommander
Indicates that one entity serves as the commanding officer or leader of a clone (or group of clones), holding authority and responsibility over them.
-
C.
commandLineTool
Indicates that an entity is a software utility intended to be executed and interacted with via a text-based command-line interface.
-
D.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
-
E.
mountCommand
Indicates that one entity issues or represents a command to mount a filesystem, device, or resource onto another entity.
- F. None of above. chosen
Provenance (4 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc30303081909c6842161ec2df46 |
completed | May 3, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:40 a.m.