Triple
T13929668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ewen Cameron |
E334955
|
entity |
| Predicate | surnamePartAssociatedWith |
P110398
|
FINISHED |
| Object | Highland clan |
—
|
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: Highland clan | Statement: [Ewen Cameron, surnamePartAssociatedWith, Highland clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surnamePartAssociatedWith Context triple: [Ewen Cameron, surnamePartAssociatedWith, Highland clan]
-
A.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
B.
familyNamePart
chosen
Indicates that one string is a component or segment of a person's full family name.
-
C.
familyName
Indicates that one entity is the family (last) name associated with another entity (typically a person).
-
D.
fatherSurname
Indicates that one entity has the same surname as, or is identified by, the family name of, the father in relation to another entity.
-
E.
familyNameSuffix
Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family name.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa900a0819095eeb1bc46b0336e |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.