Triple
T16842864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sue Perkins |
E409456
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Perkins |
E209764
|
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: Perkins | Statement: [Sue Perkins, familyName, Perkins]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perkins Context triple: [Sue Perkins, familyName, Perkins]
-
A.
Perkins
chosen
Perkins is a common English surname borne by numerous notable individuals across politics, arts, sports, and academia.
-
B.
Pitman
Pitman is a small borough in southern New Jersey known for its historic downtown and community-oriented residential character.
-
C.
Ergon
Ergon is a crystalline alien creature from the Doctor Who universe, appearing as a monster in the Fifth Doctor era.
-
D.
Pennock
Pennock is the surname of Herb Pennock, a Hall of Fame American Major League Baseball pitcher best known for his years with the New York Yankees in the 1920s.
-
E.
Brinkman
Brinkman is a surname of Germanic origin borne by various notable individuals across fields such as sports, politics, and the arts.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b35284588190a1d6238438f3e70d |
completed | April 18, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb199168819080a9ddc7534f19a7 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:24 a.m.