Triple

T19277414
Position Surface form Disambiguated ID Type / Status
Subject Adrano E482092 entity
Predicate namedAfter P63 FINISHED
Object Adranus 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: Adranus | Statement: [Adrano, namedAfter, Adranus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adranus
Context triple: [Adrano, namedAfter, Adranus]
  • A. Adranon chosen
    Adranon is the ancient name of the Sicilian town of Adrano, originally established near the slopes of Mount Etna and known for its historic and archaeological significance.
  • B. Antandrus
    Antandrus was an ancient Greek city located in the region of Mysia on the northwestern coast of Asia Minor, known for its strategic position near Mount Ida and the Gulf of Adramyttium.
  • C. Andinus
    Andinus is a lesser-known deity from ancient Illyrian religion, likely associated with local tribal worship in the western Balkans.
  • D. Yarith
    Yarith is a planet located within the Anoat sector of the Star Wars galaxy.
  • E. Aranos
    Aranos is a small town in southern Namibia known for its farming community and location within the arid Hardap Region.
  • 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_69d8e8ce54cc8190998418ff1f66ef28 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fbbd5f34819086535f28fd880411 completed April 20, 2026, 10:11 a.m.
Created at: April 10, 2026, 1:30 p.m.