Triple
T12040365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscovy duck |
E286642
|
entity |
| Predicate | domesticatedFormOf |
P31415
|
FINISHED |
| Object | wild Muscovy duck |
—
|
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: wild Muscovy duck | Statement: [Muscovy duck, domesticatedFormOf, wild Muscovy duck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticatedFormOf Context triple: [Muscovy duck, domesticatedFormOf, wild Muscovy duck]
-
A.
domesticatedForm
Indicates that one entity is the domesticated variant or descendant of another, typically wild, entity.
-
B.
domesticatedFrom
chosen
Indicates that one organism or population has been domesticated from, or originates as a domesticated form of, another organism or population.
-
C.
domesticatedFor
Indicates that one entity has been tamed and bred by another for specific human use or benefit.
-
D.
hasDomesticatedForm
Indicates that one entity has a version or counterpart that has been domesticated by humans.
-
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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.