Triple
T15551630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jasmine Trussell |
E370757
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Trussell |
E1125362
|
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: Trussell | Statement: [Jasmine Trussell, familyName, Trussell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Trussell Context triple: [Jasmine Trussell, familyName, Trussell]
-
A.
Trussell
chosen
Trussell is a family surname shared by Jabbar Trussell-Braverman through his maternal lineage.
-
B.
Challis
Challis is an English surname borne by various notable individuals across fields such as cinematography, science, and public service.
-
C.
Beveridge
Beveridge is a Scottish-origin surname most notably associated with economist and social reformer William Beveridge, whose work shaped the modern welfare state.
-
D.
Yates
Yates is a surname of English origin borne by various notable individuals across literature, politics, sports, and other fields.
-
E.
Trevelyan
Trevelyan is an English surname historically associated with several notable British families, politicians, and literary figures.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a9551288190a583e8291c35f521 |
completed | April 16, 2026, 2:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4560008c81908ebd278c3dc45045 |
completed | May 9, 2026, 2:32 p.m. |
Created at: April 10, 2026, 4:08 a.m.