Triple
T17667895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markos Botsaris |
E440434
|
entity |
| Predicate | regionOfDeath |
P21
|
FINISHED |
| Object | near Karpenisi |
—
|
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: near Karpenisi | Statement: [Markos Botsaris, regionOfDeath, near Karpenisi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfDeath Context triple: [Markos Botsaris, regionOfDeath, near Karpenisi]
-
A.
placeOfDeath
chosen
Indicates the location where an entity (typically a person or animal) died.
-
B.
traditionalPlaceOfDeath
Indicates the location where a person is customarily or culturally considered to have died, according to traditional or historical accounts.
-
C.
regionOfLoss
Indicates the anatomical or spatial area where a loss, damage, or deficit occurs or is localized.
-
D.
placeOfApotheosis
Indicates the location where a being undergoes or has undergone apotheosis, i.e., is elevated to divine or godlike status.
-
E.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46eaaaec8819086977d8a5210c44e |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:58 a.m.