Triple
T7576650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipridae |
E179376
|
entity |
| Predicate | sexualSelection |
P8592
|
FINISHED |
| Object | strong female choice based on male display |
—
|
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: strong female choice based on male display | Statement: [Pipridae, sexualSelection, strong female choice based on male display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexualSelection Context triple: [Pipridae, sexualSelection, strong female choice based on male display]
-
A.
sexualDimorphism
Indicates differences in physical characteristics between males and females of a species that are systematically associated with their sex.
-
B.
reproductiveBehavior
chosen
Indicates the actions, strategies, and interactions involved in an organism’s mating and reproduction processes.
-
C.
sexes
Indicates that one entity engages in sexual activity with another entity.
-
D.
reproductiveFeature
Indicates a relationship where an entity possesses or is characterized by a particular reproductive trait, structure, or capability.
-
E.
reproductiveType
Indicates the mode or strategy by which an organism reproduces or generates offspring.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94b7d5c81909d246845f922d969 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.