Triple
T31144303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camelus ferus |
E793878
|
entity |
| Predicate | hasDomesticatedRelative |
P31717
|
FINISHED |
| Object | Camelus bactrianus |
—
|
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: Camelus bactrianus | Statement: [Camelus ferus, hasDomesticatedRelative, Camelus bactrianus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomesticatedRelative Context triple: [Camelus ferus, hasDomesticatedRelative, Camelus bactrianus]
-
A.
domesticatedRelative
Indicates that one entity is a domesticated counterpart or close domesticated variant of another entity.
-
B.
wasDomesticatedIn
Indicates that an entity became domesticated during or within a specified time period or historical era.
-
C.
hasDomesticatedForm
chosen
Indicates that one entity has a version or counterpart that has been domesticated by humans.
-
D.
isDomesticated
Indicates that an entity has been tamed and bred by humans to live and function under human care or control.
-
E.
domesticatedBy
Indicates that one entity has been tamed and bred by another, typically a human or group, for companionship, work, or other purposes.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 9:06 p.m.