Triple
T24880506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bisset |
E622692
|
entity |
| Predicate | isSeptSurnameOf |
P104974
|
FINISHED |
| Object | Grant clan territory |
—
|
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: Grant clan territory | Statement: [Bisset, isSeptSurnameOf, Grant clan territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeptSurnameOf Context triple: [Bisset, isSeptSurnameOf, Grant clan territory]
-
A.
hasSeptSurname
chosen
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
B.
isSurname
Indicates that one entity is the family name (last name) of another entity.
-
C.
isCountableAsSurname
Indicates that something can be considered or treated as a valid surname for counting or classification purposes.
-
D.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
-
E.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:24 a.m.