Triple
T15536882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North family |
E370369
|
entity |
| Predicate | hasTitle |
P38
|
FINISHED |
| Object | Baron North |
E579944
|
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: Baron North | Statement: [North family, hasTitle, Baron North]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baron North Context triple: [North family, hasTitle, Baron North]
-
A.
Baron North
chosen
Baron North is an English hereditary peerage title in the nobility of England, historically associated with the North family.
-
B.
Baron Russell
Baron Russell is a hereditary title in the British peerage historically associated with the influential Russell family, prominent in English politics and aristocracy.
-
C.
Baron Barnard
Baron Barnard is a hereditary title in the Peerage of England historically held by the Vane family, associated with the Raby Castle estate in County Durham.
-
D.
Baron Sheffield
Baron Sheffield is a hereditary title in the British peerage historically associated with the influential Stanley family of Alderley.
-
E.
Baron Farnham
Baron Farnham is an Irish peerage title historically associated with the Anglo-Irish aristocratic Maxwell family, prominent in County Cavan.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4556ad008190a411ccd3ef0d1e89 |
completed | May 9, 2026, 2:31 p.m. |
Created at: April 10, 2026, 4:06 a.m.