Triple
T6913246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montfort Browne |
E159986
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Browne |
E325017
|
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: Browne | Statement: [Montfort Browne, hasFamilyName, Browne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Browne Context triple: [Montfort Browne, hasFamilyName, Browne]
-
A.
Browne
Browne is the surname of Lord Browne of Madingley, the prominent British businessman and former chief executive of BP.
-
B.
Browne
chosen
Browne is a surname of English and Irish origin commonly used as a family name and occasionally as a middle name.
-
C.
Paton
Paton is a surname and given name of Scottish origin, used by various notable individuals in fields such as sports, politics, and the arts.
-
D.
Barnes
Barnes is a business partner associated with Joseph Reed, likely involved in a shared professional or commercial venture.
-
E.
Barnes
Barnes is a riverside district in the London Borough of Richmond upon Thames known for its village-like atmosphere, green spaces, and historic architecture.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9dbca6c819091d8b65e54ada5d9 |
completed | March 27, 2026, 7:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7491116448190b9945e5a53056cb9 |
completed | March 28, 2026, 3:20 a.m. |
Created at: March 27, 2026, 2:25 p.m.