Triple
T38237941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anserinae |
E1013673
|
entity |
| Predicate | moltPattern |
P19651
|
FINISHED |
| Object | annual molt |
—
|
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: annual molt | Statement: [Anserinae, moltPattern, annual molt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moltPattern Context triple: [Anserinae, moltPattern, annual molt]
-
A.
maskPattern
Indicates a relationship where one entity serves as a masking template or pattern that determines which parts or aspects of another entity are revealed, hidden, or transformed.
-
B.
camouflagePattern
Indicates that one entity has a surface or visual design intended to conceal it by blending with its surroundings or disrupting its outline.
-
C.
patroonOf
Indicates a relationship in which one entity acts as a patron, sponsor, or protector providing support or resources to another entity.
-
D.
molting
chosen
Indicates the process by which an organism sheds and replaces an outer body covering, such as skin, feathers, or exoskeleton.
-
E.
wingPattern
Indicates the characteristic arrangement or design present on an entity's wings.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.