Triple
T27826203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zulu |
E702958
|
entity |
| Predicate | traditionalHomestead |
P23373
|
FINISHED |
| Object | umuzi |
—
|
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: umuzi | Statement: [Zulu, traditionalHomestead, umuzi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHomestead Context triple: [Zulu, traditionalHomestead, umuzi]
-
A.
traditionalHomeOf
chosen
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
B.
traditionalHeir
Indicates that one entity is recognized as the customary or culturally designated inheritor or successor of another entity.
-
C.
traditionalLifestyle
Indicates that an entity follows or maintains long-established customs, practices, and ways of living, typically in contrast to modern or industrialized lifestyles.
-
D.
traditionalHomeEnd
Indicates the point or time at which a traditional home, household, or customary domestic arrangement comes to an end.
-
E.
traditionalHomeDay
Indicates that a particular day is associated with traditional home-related activities, customs, or observances.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 27, 2026, 5:52 p.m.