Triple
T24802511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old May 18 Cemetery |
E620564
|
entity |
| Predicate | originalBurialGroundFor |
P60564
|
FINISHED |
| Object | victims of the Gwangju Uprising |
—
|
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: victims of the Gwangju Uprising | Statement: [Old May 18 Cemetery, originalBurialGroundFor, victims of the Gwangju Uprising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBurialGroundFor Context triple: [Old May 18 Cemetery, originalBurialGroundFor, victims of the Gwangju Uprising]
-
A.
burialPlace
Indicates the location where a person or entity is buried.
-
B.
originalBurialSiteOfRemainsLaterMovedTo
chosen
Indicates that a location was the initial burial site of human remains that were subsequently relocated to another place.
-
C.
reputedBurialPlaceOf
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
D.
firstBurial
Indicates that an entity is the earliest or initial burial associated with a person, place, or burial context.
-
E.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 4:49 a.m.