Triple
T5049121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaesong Industrial Region |
E113740
|
entity |
| Predicate | resumedOperations |
P44197
|
FINISHED |
| Object | September 2013 |
—
|
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: September 2013 | Statement: [Kaesong Industrial Region, resumedOperations, September 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumedOperations Context triple: [Kaesong Industrial Region, resumedOperations, September 2013]
-
A.
suspendedOperations
Indicates that an entity has temporarily halted or discontinued its normal operations or activities.
-
B.
resumedIn
chosen
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
C.
underlyingCommencedOperations
Indicates that the referenced underlying entity has begun its operational activities or business functions.
-
D.
resumesAfter
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
-
E.
resumedCouncil
Indicates that a council or formal deliberative body has restarted its meetings or proceedings after a pause or interruption.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.