Triple
T10498831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himantolophidae |
E247612
|
entity |
| Predicate | sexualDimorphismFeature |
P1333
|
FINISHED |
| Object | large 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: large females | Statement: [Himantolophidae, sexualDimorphismFeature, large females]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexualDimorphismFeature Context triple: [Himantolophidae, sexualDimorphismFeature, large females]
-
A.
sexualDimorphism
chosen
Indicates differences in physical characteristics between males and females of a species that are systematically associated with their sex.
-
B.
reproductiveFeature
Indicates a relationship where an entity possesses or is characterized by a particular reproductive trait, structure, or capability.
-
C.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
D.
femalePlumageFeature
Indicates that the specified plumage feature is characteristic of the female individual in a species.
-
E.
sexDeterminationDetail
Indicates the specific mechanism or factors by which an organism’s sex is determined.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098e45ec8190a02b981a06786909 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.