Triple
T18866222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Čegar Monument |
E461443
|
entity |
| Predicate | memorialForSide |
P115845
|
FINISHED |
| Object | Serbian revolutionaries |
—
|
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: Serbian revolutionaries | Statement: [Čegar Monument, memorialForSide, Serbian revolutionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialForSide Context triple: [Čegar Monument, memorialForSide, Serbian revolutionaries]
-
A.
memorialSiteFor
chosen
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
-
B.
sideCommemorated
Indicates that one side or aspect of an entity is dedicated to honoring or remembering a person, event, or concept.
-
C.
memorialType
Indicates the specific kind or category of memorial associated with an entity (e.g., plaque, statue, monument).
-
D.
memorialRole
Indicates that an entity holds a specific role, capacity, or function in relation to a memorial or commemorative context.
-
E.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a5074481908941fcbb3b3eefa2 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.