Triple
T37637353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Phalo kaTshiwo |
E936523
|
entity |
| Predicate | dynasticFoundation |
P20125
|
FINISHED |
| Object | House of Phalo |
—
|
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: House of Phalo | Statement: [King Phalo kaTshiwo, dynasticFoundation, House of Phalo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticFoundation Context triple: [King Phalo kaTshiwo, dynasticFoundation, House of Phalo]
-
A.
dynasticOrigin
chosen
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
B.
dynasticLegacy
Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
-
C.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
D.
dynasticScope
Indicates the range or extent of influence, authority, or relevance associated with a particular dynasty or dynastic period.
-
E.
dynasticStructure
Indicates the hierarchical organization and succession relationships within a dynasty or ruling family.
- 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_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.