Triple
T16334545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurotragus |
E396641
|
entity |
| Predicate | hasSexualDimorphismTrait |
P1333
|
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: [Taurotragus, hasSexualDimorphismTrait, males larger than females]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSexualDimorphismTrait Context triple: [Taurotragus, hasSexualDimorphismTrait, males larger than females]
-
A.
sexualDimorphism
chosen
Indicates differences in physical characteristics between males and females of a species that are systematically associated with their sex.
-
B.
hasAsexualMorph
Indicates that an entity possesses or is associated with an asexual morphological form in its life cycle.
-
C.
hasSexualityCharacteristic
Indicates that an entity possesses a specific sexual orientation or sexuality-related characteristic.
-
D.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
-
E.
hasGenderVariant
Indicates that one entity is a gender-specific form or variant of another entity.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e29db88190936a07deb5b1c1e3 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.