Triple
T2972225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis Bellamy |
E80306
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bellamy |
E257517
|
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: Bellamy | Statement: [Francis Bellamy, familyName, Bellamy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bellamy Context triple: [Francis Bellamy, familyName, Bellamy]
-
A.
Bellamy
chosen
Bellamy is a surname of English and French origin borne by various notable individuals across fields such as sports, politics, and the arts.
-
B.
Myles
Myles is a masculine given name of English origin, historically associated with figures such as Mayflower military leader Myles Standish.
-
C.
Jono
Jono is a casual diminutive or nickname commonly used for the given name Jonathan.
-
D.
Jayme
Jayme is a given name, typically a variant spelling of Jamie, used for people of any gender.
-
E.
Kaylon
Kaylon are a highly advanced artificial machine species from the Orville universe, known for their collective intelligence and often adversarial stance toward biological life.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998656948190ba79d7196d735f34 |
completed | March 8, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0fca910e481909c1d93b512a779aa |
completed | March 11, 2026, 5:24 a.m. |
Created at: March 8, 2026, 2:58 p.m.