Triple

T5189655
Position Surface form Disambiguated ID Type / Status
Subject Paul George E117119 entity
Predicate familyName P18 FINISHED
Object George E372351 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: George | Statement: [Paul George, familyName, George]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: George
Context triple: [Paul George, familyName, George]
  • A. George
    George is the first name of George Washington, the first President of the United States and a key leader in the American Revolutionary War.
  • B. George
    George is the heroic protagonist of the fantasy film "The Magic Sword," known for embarking on a perilous quest to rescue a princess from an evil sorcerer.
  • 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 chosen
    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_69bd44620ff48190bcac01782107a397 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd79c732b48190af62dfffcbc5e3a6 completed March 20, 2026, 4:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69beefb6eaac8190a34b01c6e30b41dc completed March 21, 2026, 7:21 p.m.
Created at: March 20, 2026, 1:46 p.m.