Triple
T37637289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AmaGcaleka |
E936521
|
entity |
| Predicate | traditionalLawfulHead |
P133279
|
FINISHED |
| Object | king |
—
|
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: king | Statement: [AmaGcaleka, traditionalLawfulHead, king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLawfulHead Context triple: [AmaGcaleka, traditionalLawfulHead, king]
-
A.
traditionalRule
Indicates that an entity follows, embodies, or is governed by a customary or long-established rule or norm.
-
B.
traditionalLawGivingSite
Indicates a location that is traditionally recognized as the place where laws or legal codes were formally given or proclaimed.
-
C.
traditionalHead
chosen
Indicates that one entity serves as the customary or culturally recognized leader or chief of another entity.
-
D.
customaryLaw
Indicates that a relationship, behavior, or rule is governed by unwritten, traditional norms and practices recognized as binding within a community or group.
-
E.
traditionalSect
Indicates that an entity belongs to or is associated with a religious or ideological sect that follows long-established, customary beliefs and practices.
- 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_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:18 p.m.