Triple
T26737460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egretta |
E674154
|
entity |
| Predicate | plumageDimorphism |
P162173
|
FINISHED |
| Object | some species show white and dark morphs |
—
|
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: some species show white and dark morphs | Statement: [Egretta, plumageDimorphism, some species show white and dark morphs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plumageDimorphism Context triple: [Egretta, plumageDimorphism, some species show white and dark morphs]
-
A.
plumageFeature
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
B.
femalePlumageFeature
Indicates that the specified plumage feature is characteristic of the female individual in a species.
-
C.
maleBreedingPlumageFeature
Indicates that the relationship involves a physical or visual characteristic specifically associated with a male’s breeding-season plumage.
-
D.
plumageMarkingsColor
Indicates the color of the markings or patterns present on an entity's plumage.
-
E.
malePlumage
Indicates that the specified plumage belongs to or characterizes the male individual of a species.
- F. None of above. chosen
Provenance (4 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 3:48 a.m.