Triple

T22873464
Position Surface form Disambiguated ID Type / Status
Subject The Book of Phoenix E567259 entity
Predicate mainCharacter P1183 FINISHED
Object Phoenix 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: Phoenix | Statement: [The Book of Phoenix, mainCharacter, Phoenix]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Phoenix
Context triple: [The Book of Phoenix, mainCharacter, Phoenix]
  • A. Phoenix
    Phoenix is a wise and loyal elder warrior and mentor in Greek mythology, best known for guiding and advising Achilles during the Trojan War.
  • B. Phoenix
    Phoenix is a historic London theatre located on Drury Lane, known for staging a wide range of plays and musicals.
  • C. Phoenix
    Phoenix is the capital and largest city of the U.S. state of Arizona, known for its desert climate, rapid growth, and role as a major economic and cultural center in the American Southwest.
  • D. Phoenix chosen
    Phoenix is the mythical bird that cyclically regenerates from its own ashes, symbolizing rebirth and renewal.
  • E. Phoenix
    Phoenix is a residential suburb within the greater Milnerton area of Cape Town, South Africa.
  • 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f55c4b88190adb49871e496ca54 completed April 29, 2026, 3:47 a.m.
Created at: April 17, 2026, 3:39 p.m.