Triple
T19701601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panmungak |
E473109
|
entity |
| Predicate | securityForcesPresent |
P80479
|
FINISHED |
| Object | Korean People's Army guards |
—
|
LITERAL 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: Korean People's Army guards | Statement: [Panmungak, securityForcesPresent, Korean People's Army guards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityForcesPresent Context triple: [Panmungak, securityForcesPresent, Korean People's Army guards]
-
A.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
B.
policePresence
chosen
Indicates that law enforcement officers are present at or monitoring a particular location, event, or situation.
-
C.
securityArrangements
Indicates the existence, nature, or details of protective measures or safeguards established between or around entities.
-
D.
securityLocation
Indicates the place or area where security-related activities, measures, or responsibilities are situated or applied.
-
E.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
- F. None of above.
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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b667908190841bb5fb7bfdb3f7 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.