Triple
T35146909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacSheamais |
E1014865
|
entity |
| Predicate | isFamilyNameIn |
P66749
|
FINISHED |
| Object | Scotland |
—
|
NE NERFINISHED |
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: Scotland | Statement: [MacSheamais, isFamilyNameIn, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFamilyNameIn Context triple: [MacSheamais, isFamilyNameIn, Scotland]
-
A.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
B.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
C.
familyNameIn
chosen
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
D.
isNotFamilyName
Indicates that a given name or string does not function as a family name (surname) for the specified entity.
-
E.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78cb0fe448190b8f11584fdf36c11 |
completed | May 3, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.