Triple

T26134461
Position Surface form Disambiguated ID Type / Status
Subject Basta village E659338 entity
Predicate hasSiteTypeNearby P120316 FINISHED
Object archaeological site 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: archaeological site | Statement: [Basta village, hasSiteTypeNearby, archaeological site]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSiteTypeNearby
Context triple: [Basta village, hasSiteTypeNearby, archaeological site]
  • A. hasNearbySiteType chosen
    Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
  • B. hasNearbyInfrastructureType
    Indicates that an entity is located close to infrastructure of a specified type.
  • C. hasNearbyFacility
    Indicates that one entity is located close to or in the vicinity of a particular facility.
  • D. hasNearbyPropertyType
    Indicates that one entity has another entity of a specified property type located in close physical proximity to it.
  • E. nearbySitePartOf
    Indicates that one site or site component is located close to and is considered part of another, larger site or site component.
  • 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_69ee5bc3c20c8190bf2cf272f4170e95 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f661b58ac48190907b6c6e9ccc2c59 completed May 2, 2026, 8:42 p.m.
PD Predicate disambiguation batch_69f660eea4648190b0d5e24293607813 completed May 2, 2026, 8:39 p.m.
Created at: April 26, 2026, 8:16 p.m.