Triple
T3658124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Bruce, 7th Earl of Elgin |
E77582
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bruce |
E52442
|
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: Bruce | Statement: [Thomas Bruce, 7th Earl of Elgin, familyName, Bruce]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bruce Context triple: [Thomas Bruce, 7th Earl of Elgin, familyName, Bruce]
-
A.
Bruce
chosen
Bruce is a masculine given name of English and Scottish origin, commonly associated with figures in music, film, and popular culture.
-
B.
Brian
Brian is a masculine given name of Irish origin that has become widely used in English-speaking countries.
-
C.
Bro
Bro is a locality in Stockholm County, Sweden, known as one of the main population centers within Upplands-Bro Municipality.
-
D.
Ben
Ben is a common given name, typically used as a short form of names like Benedict or Benjamin.
-
E.
Brad
Brad is a masculine given name commonly used in English-speaking countries, often as a short form of Bradley or Bradford.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d48a2081908ac0f76d548a53ee |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4884071c881909daae2f3c510d399 |
completed | March 13, 2026, 9:57 p.m. |
Created at: March 8, 2026, 3:24 p.m.