Triple
T30121197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | blue-gray tanager |
E765565
|
entity |
| Predicate | malePlumageSimilarity |
P162173
|
FINISHED |
| Object | similar to female |
—
|
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: similar to female | Statement: [blue-gray tanager, malePlumageSimilarity, similar to female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: malePlumageSimilarity Context triple: [blue-gray tanager, malePlumageSimilarity, similar to female]
-
A.
malePlumage
Indicates that the specified plumage belongs to or characterizes the male individual of a species.
-
B.
plumageDimorphism
chosen
Indicates that there is a difference in plumage characteristics between two groups (typically sexes or age classes) within a species.
-
C.
maleBreedingPlumageFeature
Indicates that the relationship involves a physical or visual characteristic specifically associated with a male’s breeding-season plumage.
-
D.
plumageMorph
Indicates a relationship where an entity is characterized by a particular form or variant of plumage.
-
E.
femalePlumageFeature
Indicates that the specified plumage feature is characteristic of the female individual in a species.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67deb0888819090b6d69cd598c34c |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:13 p.m.