Triple
T22901899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bečani necropolis |
E568339
|
entity |
| Predicate | tombstoneType |
P95911
|
FINISHED |
| Object | stećci |
—
|
NE NERFINISHED |
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ćci | Statement: [Bečani necropolis, tombstoneType, stećci]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: stećci Context triple: [Bečani necropolis, tombstoneType, stećci]
-
A.
stećci
chosen
Stećci are monumental medieval stone tombstones, often richly decorated with carvings and inscriptions, found primarily across Bosnia and Herzegovina and neighboring regions of the western Balkans.
-
B.
Stec
Stec is a Polish surname borne by various notable individuals in fields such as aviation, sports, and the arts.
-
C.
STE
STE is the vehicle registration code assigned to the district of Lichtenfels in Germany.
-
D.
STE
STE is the public agency that operates Mexico City’s electric transport services, including trolleybuses and light rail.
-
E.
Stalać
Stalać is a village in central Serbia known for its strategic location near the confluence of major rivers and important transportation routes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18016d8e481908fc47d003156b800 |
completed | April 29, 2026, 3:50 a.m. |
Created at: April 17, 2026, 3:41 p.m.