Triple
T23902037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of the Workers' Party of Korea |
E601071
|
entity |
| Predicate | symbolOfHammer |
P129
|
FINISHED |
| Object | industrial workers |
—
|
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: industrial workers | Statement: [Flag of the Workers' Party of Korea, symbolOfHammer, industrial workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolOfHammer Context triple: [Flag of the Workers' Party of Korea, symbolOfHammer, industrial workers]
-
A.
hammerRepresents
Indicates that one entity serves as a symbolic or representative depiction of a hammer in relation to another entity.
-
B.
hammerType
Indicates the specific kind or category of hammer associated with an entity.
-
C.
symbolicWeapon
Indicates a relationship where something functions as a symbolic or emblematic weapon for an entity, representing power, threat, or conflict rather than serving as a literal physical armament.
-
D.
symbolOnInsignia
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
E.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdde91d081908df44442a20e0fd2 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.