Triple
T35849124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cush (son of Ham) |
E1036298
|
entity |
| Predicate | traditionallyRegardedAsAncestorOf |
P149753
|
FINISHED |
| Object | Cushites |
—
|
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: Cushites | Statement: [Cush (son of Ham), traditionallyRegardedAsAncestorOf, Cushites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyRegardedAsAncestorOf Context triple: [Cush (son of Ham), traditionallyRegardedAsAncestorOf, Cushites]
-
A.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
B.
proposedAsAncestralOriginOf
Indicates that something is suggested or hypothesized to be the ancestral source or origin of something else.
-
C.
allegedAncestor
chosen
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
-
D.
ancestralDomainOf
Indicates that one entity is the original or historically prior domain from which another domain is derived or descended.
-
E.
traditionInheritedFrom
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.