Triple

T4845912
Position Surface form Disambiguated ID Type / Status
Subject Tina Charles E108289 entity
Predicate familyName P18 FINISHED
Object Charles E13673 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: Charles | Statement: [Tina Charles, familyName, Charles]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Charles
Context triple: [Tina Charles, familyName, Charles]
  • A. Charles chosen
    Charles is a masculine given name of Germanic origin that has been widely used across Europe and the English-speaking world, borne by numerous historical figures, royalty, and notable individuals.
  • B. Edward
    Edward is a masculine given name of English origin, historically associated with kings of England and notable figures such as U.S. Senator Edward M. Kennedy.
  • C. George
    George is a masculine given name of Greek origin, commonly used in English-speaking countries and borne by numerous historical and contemporary figures.
  • D. George
    George is a common masculine given name of Greek origin, meaning "farmer" or "earthworker."
  • E. George
    George is a masculine given name of Greek origin meaning "farmer" or "earthworker," widely used in English-speaking and many other cultures.
  • 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_69bd4409b264819085ab855f3eb5381a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d19784c81908e256ea23889192b completed March 20, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69be5cd6dbcc8190b802eeb6d74fd37d completed March 21, 2026, 8:54 a.m.
Created at: March 20, 2026, 1:25 p.m.