Triple
T2663157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anseriformes |
E54770
|
entity |
| Predicate | domesticatedSpecies |
P31717
|
FINISHED |
| Object | domestic 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: domestic duck | Statement: [Anseriformes, domesticatedSpecies, domestic duck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticatedSpecies Context triple: [Anseriformes, domesticatedSpecies, domestic duck]
-
A.
notableDomesticatedSpecies
Indicates that the subject is a species that is particularly well-known or significant as a domesticated animal.
-
B.
domesticatedMembers
Indicates that certain members of a group or species have been tamed and adapted to live in close association with humans, typically under human care or control.
-
C.
domesticatedFor
Indicates that one entity has been tamed and bred by another for specific human use or benefit.
-
D.
hasDomesticatedForm
chosen
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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96b9f1c8190a8a9460ca88a9aaf |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.