Triple

T14244136
Position Surface form Disambiguated ID Type / Status
Subject Laura Petrie E353086 entity
Predicate hasLastName P18 FINISHED
Object Petrie E376764 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: Petrie | Statement: [Laura Petrie, hasLastName, Petrie]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Petrie
Context triple: [Laura Petrie, hasLastName, Petrie]
  • A. Petrie chosen
    Petrie is a surname most notably associated with Geoff Petrie, a former American professional basketball player and executive.
  • B. Pinchbeck
    Pinchbeck is a village and civil parish in the South Holland district of Lincolnshire, England, known for its agricultural surroundings and proximity to the town of Spalding.
  • C. Elspie
    Elspie is a feminine given name, typically considered a Scottish or diminutive variant of the name Elsie.
  • D. Polton
    Polton is a small village in Midlothian, Scotland, situated near the River North Esk and historically associated with paper milling.
  • E. Shadbolt
    Shadbolt is a surname most notably associated with Sir Nigel Shadbolt, a prominent British computer scientist and artificial intelligence researcher.
  • 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_69d8278adc7c8190a9218d69bce3c4e6 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6245d6a481909ef665748cd4d64c completed April 14, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd282571ec819080d187ecec3ed925 completed May 8, 2026, 12:02 a.m.
Created at: April 10, 2026, 1:08 a.m.