Triple
T2116052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Predynastic Egypt |
E43811
|
entity |
| Predicate | domesticates |
P10558
|
FINISHED |
| Object | cattle |
—
|
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: cattle | Statement: [Predynastic Egypt, domesticates, cattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticates Context triple: [Predynastic Egypt, domesticates, cattle]
-
A.
domestication
Indicates the process by which humans tame and genetically adapt a wild species over time so it can live and reproduce under human control or in close association with people.
-
B.
domesticatedFor
chosen
Indicates that one entity has been tamed and bred by another for specific human use or benefit.
-
C.
domesticatedBy
Indicates that one entity has been tamed and bred by another, typically a human or group, for companionship, work, or other purposes.
-
D.
notableDomesticatedSpecies
Indicates that the subject is a species that is particularly well-known or significant as a domesticated animal.
-
E.
domesticatedFrom
Indicates that one organism or population has been domesticated from, or originates as a domesticated form of, another organism or population.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb2dfd3c81909b5e2996bc324301 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.