Triple
T30121804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phrygilus gayi |
E765579
|
entity |
| Predicate | sexDescriptionMale |
P78622
|
FINISHED |
| Object | male has more distinct grey hood |
—
|
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 has more distinct grey hood | Statement: [Phrygilus gayi, sexDescriptionMale, male has more distinct grey hood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexDescriptionMale Context triple: [Phrygilus gayi, sexDescriptionMale, male has more distinct grey hood]
-
A.
maleFeature
chosen
Indicates that the subject possesses a characteristic or attribute typically associated with males.
-
B.
sexType
Indicates the specific category or type of sexual activity or sexual relationship involved between entities.
-
C.
maleDisplay
Indicates that a male individual is performing a display behavior directed toward another entity, typically for attraction, competition, or signaling.
-
D.
sexStatus
Indicates whether and how a sexual relationship or sexual activity exists or has occurred between the related entities.
-
E.
maleEquivalent
Indicates that one entity is the corresponding male counterpart or equivalent 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67debf2308190b955958a85154a24 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:13 p.m.