Triple
T15813889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Lascelles |
E383424
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Lascelles |
E81897
|
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: Lascelles | Statement: [House of Lascelles, hasSurname, Lascelles]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lascelles Context triple: [House of Lascelles, hasSurname, Lascelles]
-
A.
Lascelles
chosen
Lascelles is a British aristocratic family name historically associated with the Earls of Harewood and close ties to the royal family.
-
B.
Challis
Challis is an English surname borne by various notable individuals across fields such as cinematography, science, and public service.
-
C.
Scarphe
Scarphe is a figure from Greek mythology known primarily as the wife of Aeson, the father of the hero Jason.
-
D.
Vassall
Vassall is an English surname historically associated with notable figures in British public life and espionage.
-
E.
Craufurd
Craufurd is an alternative spelling of the surname Crawford, historically borne by several notable Scottish families and individuals.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a1571881909488728f123865ad |
completed | April 16, 2026, 11:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9993c86c8190b1d106af7537080a |
completed | May 9, 2026, 8:31 p.m. |
Created at: April 10, 2026, 4:49 a.m.