Triple
T23493888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hima |
E571649
|
entity |
| Predicate | ethnoHistoricalCategory |
P76422
|
FINISHED |
| Object | Hamitic |
—
|
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: Hamitic | Statement: [Hima, ethnoHistoricalCategory, Hamitic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnoHistoricalCategory Context triple: [Hima, ethnoHistoricalCategory, Hamitic]
-
A.
ethnoHistoricRegion
Indicates a relationship where an entity is associated with a geographic region defined by its historical and ethnic or cultural characteristics.
-
B.
historicalEthnicGroups
chosen
Indicates that there is a historically attested ethnic group or groups associated with the subject entity.
-
C.
regionHistoricalEthnonym
Indicates that a region is historically known or referred to by a particular ethnonym associated with a people or ethnic group.
-
D.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
E.
ethnicHistory
Indicates a relationship where one entity documents, describes, or is associated with the historical development, experiences, or heritage of an ethnic group.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7de1ab88190b6c2441c63a99713 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.