Triple
T19097940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Forbes |
E467455
|
entity |
| Predicate | hasSurnameDerivedFrom |
P54694
|
FINISHED |
| Object | territory of Forbes in Aberdeenshire |
—
|
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: territory of Forbes in Aberdeenshire | Statement: [House of Forbes, hasSurnameDerivedFrom, territory of Forbes in Aberdeenshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameDerivedFrom Context triple: [House of Forbes, hasSurnameDerivedFrom, territory of Forbes in Aberdeenshire]
-
A.
familyNameDerivedFrom
chosen
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
B.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
C.
hasPatronymicDerivative
Indicates that one name or term is derived from another by forming a patronymic, typically expressing descent or lineage from a person.
-
D.
isSurname
Indicates that one entity is the family name (last name) of another entity.
-
E.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e36b279c819091a8d51f044bc644 |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.