Triple
T16510450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Damaliscus |
E401045
|
entity |
| Predicate | hornSexualDimorphism |
P1333
|
FINISHED |
| Object | both sexes horned in most species |
—
|
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: both sexes horned in most species | Statement: [Damaliscus, hornSexualDimorphism, both sexes horned in most species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hornSexualDimorphism Context triple: [Damaliscus, hornSexualDimorphism, both sexes horned in most species]
-
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.
sexes
Indicates that one entity engages in sexual activity with another entity.
-
D.
flowerSex
Indicates that one entity has a specified sexual characteristic or reproductive role in relation to a flower.
-
E.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e55fe7c8190abc957bdd326d1bc |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.