Triple

T939657
Position Surface form Disambiguated ID Type / Status
Subject Sibyl Rock E20275 entity
Predicate namedAfter P63 FINISHED
Object Sibyl E114418 NE 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: Sibyl | Statement: [Sibyl Rock, namedAfter, Sibyl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sibyl
Context triple: [Sibyl Rock, namedAfter, Sibyl]
  • A. Sibyl chosen
    Sibyl is a prophetic figure from ancient Greco-Roman tradition, typically depicted as a woman endowed with divine insight and the power of inspired oracles.
  • B. Daphne
    Daphne is a nymph from Greek mythology best known for being pursued by Apollo and transformed into a laurel tree to escape him.
  • C. Daphne
    Daphne is a coastal city in Baldwin County, Alabama, situated along the eastern shore of Mobile Bay.
  • D. Praxeas
    Praxeas was an early Christian theologian known for promoting a modalistic view of the Trinity that was later deemed heretical by mainstream church authorities.
  • E. Hera Gamelia
    Hera Gamelia is an aspect of the Greek goddess Hera worshipped as the protector of marriage and the wedding rite.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a493b0270c81909e6c9ce310f6aa55 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b38b7da08190ac0853655dab678a completed March 1, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac1cd569a4819082687be40145331e completed March 7, 2026, 12:40 p.m.
Created at: March 1, 2026, 7:40 p.m.