Triple
T36227444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porichthyidae |
E891140
|
entity |
| Predicate | courtship |
P139538
|
FINISHED |
| Object | male humming calls to attract females |
—
|
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: male humming calls to attract females | Statement: [Porichthyidae, courtship, male humming calls to attract females]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtship Context triple: [Porichthyidae, courtship, male humming calls to attract females]
-
A.
courtshipMode
Indicates the manner or strategy by which one entity engages in behaviors intended to attract or win the favor of another for a romantic or reproductive relationship.
-
B.
courtships
chosen
Indicates that one entity engages in courtship behavior toward another, typically as part of initiating or maintaining a romantic or mating relationship.
-
C.
asksToMarry
Indicates that one entity proposes marriage to another, requesting that they become spouses.
-
D.
destinedToMarry
Indicates that two entities are fated or predetermined to marry each other in the future.
-
E.
encouragesRomanceBetween
Indicates that one entity promotes, supports, or fosters a romantic relationship between two other entities.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b59fb78c8190a5f9e15688b1cdf1 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.