Triple
T32209420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatolian Neolithic |
E822758
|
entity |
| Predicate | usedDomesticate |
P32570
|
FINISHED |
| Object | wheat |
—
|
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: wheat | Statement: [Anatolian Neolithic, usedDomesticate, wheat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDomesticate Context triple: [Anatolian Neolithic, usedDomesticate, wheat]
-
A.
domesticatedFor
Indicates that one entity has been tamed and bred by another for specific human use or benefit.
-
B.
isDomesticated
Indicates that an entity has been tamed and bred by humans to live and function under human care or control.
-
C.
domesticatedBy
chosen
Indicates that one entity has been tamed and bred by another, typically a human or group, for companionship, work, or other purposes.
-
D.
wasDomesticatedIn
Indicates that an entity became domesticated during or within a specified time period or historical era.
-
E.
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.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb90bb908190a7b01f36dc123cf1 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:37 a.m.