Triple
T37637288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AmaGcaleka |
E936521
|
entity |
| Predicate | usesSurnameCluster |
P49952
|
FINISHED |
| Object | Gcaleka-related surnames |
—
|
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: Gcaleka-related surnames | Statement: [AmaGcaleka, usesSurnameCluster, Gcaleka-related surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSurnameCluster Context triple: [AmaGcaleka, usesSurnameCluster, Gcaleka-related surnames]
-
A.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
B.
associatedSurname
chosen
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
C.
possibleSurnameUsage
Indicates that an entity can potentially be used or recognized as a surname for another entity.
-
D.
hasLastNameInCommonWith
Indicates that two entities share the same last name.
-
E.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:18 p.m.