Triple
T34712672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pondoland |
E1000687
|
entity |
| Predicate | historicPeople |
P34335
|
FINISHED |
| Object | Faku kaNgqungqushe |
—
|
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: Faku kaNgqungqushe | Statement: [Pondoland, historicPeople, Faku kaNgqungqushe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicPeople Context triple: [Pondoland, historicPeople, Faku kaNgqungqushe]
-
A.
historicalPeople
chosen
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
-
B.
historicalPeopleCenter
Indicates a relationship where a center, institution, or focal point is dedicated to, focused on, or primarily concerned with historical people.
-
C.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
D.
roleInHumanHistory
Indicates the function, influence, or significance that an entity has had within the course of human history.
-
E.
historicResident
Indicates that an entity lived or resided in a place during a historically significant period or in the past.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
Created at: May 3, 2026, 3:59 p.m.