Triple
T3005793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lascelles family |
E81897
|
entity |
| Predicate | surnameOrigin |
P3325
|
FINISHED |
| Object | English-language surname |
—
|
LITERAL 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: English-language surname | Statement: [Lascelles family, surnameOrigin, English-language surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surnameOrigin Context triple: [Lascelles family, surnameOrigin, English-language surname]
-
A.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
C.
surnameVariant
Indicates that one surname is an alternative spelling, form, or variation of another surname.
-
D.
JapaneseNameOrigin
Indicates that one entity’s name originates from or is derived from the Japanese language or naming tradition in relation to another entity.
-
E.
popularEtymology
Indicates that an etymological explanation is based on common belief or folk interpretation rather than on historically or linguistically accurate origins.
- F. None of above.
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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a15ad9c81908255003bdb38d603 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.