Triple

T17334605
Position Surface form Disambiguated ID Type / Status
Subject Jasper Western E420902 entity
Predicate hasGivenName P17 FINISHED
Object Jasper E753227 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: Jasper | Statement: [Jasper Western, hasGivenName, Jasper]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jasper
Context triple: [Jasper Western, hasGivenName, Jasper]
  • A. Jasper
    Jasper is a cloud-based Internet of Things (IoT) platform company that provides tools for managing and monetizing connected devices and services.
  • B. Jasper
    Jasper is a powerful and antagonistic Gem warrior in the animated series "Steven Universe," known for her brute strength, loyalty to Homeworld, and complex rivalry with the Crystal Gems.
  • C. Jasper chosen
    Jasper is a surname of English origin borne by various individuals, including Margaret Jasper.
  • D. Jasper
    Jasper is a small city in Hamilton County, North Central Florida, known as a rural community and local government seat.
  • E. Jasper
    Jasper is a small city in northwestern Alabama known historically for its coal mining and role in the state's industrial development.
  • 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_69d889d3adc881909319f1edb8d2a956 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a1125d88190b67243b30d93ce1c completed April 19, 2026, 2:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a018c5205088190aa724873c6296b1e completed May 11, 2026, 7:59 a.m.
Created at: April 10, 2026, 5:43 a.m.