Triple
T21858872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boljun necropolis |
E539704
|
entity |
| Predicate | tombstoneForm |
P145952
|
FINISHED |
| Object | monolithic stone slabs |
—
|
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: monolithic stone slabs | Statement: [Boljun necropolis, tombstoneForm, monolithic stone slabs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tombstoneForm Context triple: [Boljun necropolis, tombstoneForm, monolithic stone slabs]
-
A.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
B.
associatedTomb
Indicates a relationship in which an entity is linked to or connected with a particular tomb, such as by burial, ownership, dedication, or commemoration.
-
C.
tombOwnership
Indicates a relationship in which one entity holds legal or traditional ownership rights over a specific tomb.
-
D.
formerGraveOf
Indicates that a location once served as the grave of an entity, but no longer does (e.g., the remains have been moved or the grave has been removed).
-
E.
afterlifeForm
Indicates the form, state, or manifestation an entity takes in an afterlife or post-mortem existence.
- F. None of above. chosen
Provenance (4 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63944d88190b6bd5e6ba4cc8ec1 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:56 p.m.