Triple
T26996250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buceros bicornis |
E679985
|
entity |
| Predicate | sexDifference |
P161758
|
FINISHED |
| Object | males larger than 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: males larger than females | Statement: [Buceros bicornis, sexDifference, males larger than females]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexDifference Context triple: [Buceros bicornis, sexDifference, males larger than females]
-
A.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
B.
sexType
Indicates the specific category or type of sexual activity or sexual relationship involved between entities.
-
C.
genderSpecificity
Indicates whether the relationship or action applies specifically to a particular gender or is gender-neutral.
-
D.
sexStatus
Indicates whether and how a sexual relationship or sexual activity exists or has occurred between the related entities.
-
E.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
- F. None of above. chosen
Provenance (4 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6219447488190a7eac0d954c85555 |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 6:54 a.m.