Triple
T21786637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mramorje necropolis at Perućac |
E537853
|
entity |
| Predicate | hasTombstoneType |
P145933
|
FINISHED |
| Object | stećak |
—
|
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: stećak | Statement: [Mramorje necropolis at Perućac, hasTombstoneType, stećak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTombstoneType Context triple: [Mramorje necropolis at Perućac, hasTombstoneType, stećak]
-
A.
hasFormulaOnTombstone
Indicates that a tombstone bears a specific written formula or inscription on it.
-
B.
hasCheckpointType
Indicates that a checkpoint is associated with a specific type or category defining its role or characteristics.
-
C.
hasApproximateNumberOfTombs
Indicates that an entity is associated with a tomb count that is approximate rather than exact.
-
D.
hasCemeteryType
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
-
E.
hasReclamationType
Indicates the specific method or category of reclamation associated with an entity, such as how land, materials, or resources are recovered or restored.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621b5d6881908b74bc999c94fa3d |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:52 p.m.