Triple
T26521884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Workshops |
E669977
|
entity |
| Predicate | closureCaused |
P60866
|
FINISHED |
| Object | June Days Uprising |
—
|
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: June Days Uprising | Statement: [National Workshops, closureCaused, June Days Uprising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureCaused Context triple: [National Workshops, closureCaused, June Days Uprising]
-
A.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
B.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
C.
closureBy
chosen
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
D.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
E.
closureDetail
Indicates the specific manner or circumstances under which an event, process, or entity is brought to an end or formally closed.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c35b5481909ef85d87d1604be9 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:28 a.m.