Triple
T28743602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galbulidae |
E731306
|
entity |
| Predicate | plumageSexualDimorphism |
P162173
|
FINISHED |
| Object | present in many species |
—
|
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: present in many species | Statement: [Galbulidae, plumageSexualDimorphism, present in many species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plumageSexualDimorphism Context triple: [Galbulidae, plumageSexualDimorphism, present in many species]
-
A.
plumageDimorphism
chosen
Indicates that there is a difference in plumage characteristics between two groups (typically sexes or age classes) within a species.
-
B.
plumageFeature
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
C.
femalePlumageFeature
Indicates that the specified plumage feature is characteristic of the female individual in a species.
-
D.
plumageMorph
Indicates a relationship where an entity is characterized by a particular form or variant of plumage.
-
E.
maleBreedingPlumageFeature
Indicates that the relationship involves a physical or visual characteristic specifically associated with a male’s breeding-season plumage.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657b587288190804872c8ebbf94a4 |
completed | May 2, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6:03 a.m.