Triple
T18429634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borutta |
E450229
|
entity |
| Predicate | hasHeritageTypeNearby |
P55205
|
FINISHED |
| Object | prehistoric necropolis |
—
|
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: prehistoric necropolis | Statement: [Borutta, hasHeritageTypeNearby, prehistoric necropolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageTypeNearby Context triple: [Borutta, hasHeritageTypeNearby, prehistoric necropolis]
-
A.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
B.
heritageSiteTypeNearby
chosen
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
C.
hasNearbyTownType
Indicates that one entity has, in its vicinity, a town of a specified type or classification.
-
D.
hasNearbyCulturalDistrict
Indicates that an entity is located close to a designated cultural district or area with concentrated cultural activities.
-
E.
hasHeritageStatusWithin
Indicates that something holds a recognized heritage designation or status within a specified area, jurisdiction, or context.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b15e2e081908c96c5678ff4b941 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 11:26 a.m.