Triple
T33901025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porichthys notatus |
E869046
|
entity |
| Predicate | TypeIMaleBehavior |
P78622
|
FINISHED |
| Object | nest building and courtship humming |
—
|
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: nest building and courtship humming | Statement: [Porichthys notatus, TypeIMaleBehavior, nest building and courtship humming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TypeIMaleBehavior Context triple: [Porichthys notatus, TypeIMaleBehavior, nest building and courtship humming]
-
A.
maleFeature
chosen
Indicates that the subject possesses a characteristic or attribute typically associated with males.
-
B.
isMaleCharacter
Indicates that the referenced character is identified as male.
-
C.
genderDominance
Indicates a relationship where one gender holds greater power, control, or influence over another within a given context or system.
-
D.
playsGender
Indicates that one entity performs or assumes a particular gender role or identity in a given context.
-
E.
femaleBehavior
Indicates that the behavior or actions being referred to are characteristic of, or typically associated with, females in the given context.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.