Triple

T4494061
Position Surface form Disambiguated ID Type / Status
Subject Jacksen E100648 entity
Predicate hasSpellingVariant P457 FINISHED
Object Jaxen E415121 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: Jaxen | Statement: [Jacksen, hasSpellingVariant, Jaxen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jaxen
Context triple: [Jacksen, hasSpellingVariant, Jaxen]
  • A. Jaxen chosen
    Jaxen is a modern given name, typically used for boys, that serves as an alternative spelling of the name Jaxon.
  • B. Xanga
    Xanga is a now largely defunct early 2000s social networking and blogging platform that allowed users to create personal blogs, share posts, and interact through comments and subscriptions.
  • C. Plumtree
    Plumtree is a small border town in southwestern Zimbabwe that serves as a key road and rail gateway between Zimbabwe and Botswana.
  • D. Sparx
    Sparx is the loyal dragonfly companion and health indicator who follows Spyro throughout the Spyro the Dragon video game series.
  • E. Rubinius
    Rubinius is an alternative Ruby implementation featuring a virtual machine and just-in-time compilation, designed for high performance and concurrency.
  • 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_69bd43cdf15081909a4fa2585ff63b3e completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5572c60881909101b4e65dd5de06 completed March 20, 2026, 2:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69bd67ba4d4881909fe32902507bcbe3 completed March 20, 2026, 3:28 p.m.
Created at: March 20, 2026, 1 p.m.