Triple
T6972066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otidiformes |
E161619
|
entity |
| Predicate | courtshipDisplay |
P68321
|
FINISHED |
| Object | elaborate male displays |
—
|
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: elaborate male displays | Statement: [Otidiformes, courtshipDisplay, elaborate male displays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtshipDisplay Context triple: [Otidiformes, courtshipDisplay, elaborate male displays]
-
A.
matingDisplay
chosen
Indicates a behavior or display performed by one organism to attract or court a potential mate.
-
B.
reproductiveBehavior
Indicates the actions, strategies, and interactions involved in an organism’s mating and reproduction processes.
-
C.
rivalForMarriageOf
Indicates that one entity is a romantic competitor with another entity for the opportunity to marry a specific third entity.
-
D.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
E.
marriagePattern
Indicates the typical form or structure of a marriage relationship, such as how partners are selected, organized, or related within a social or cultural system.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db398f10819096d34b179ccb20d5 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.