Triple
T30758408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pink salmon |
E783154
|
entity |
| Predicate | maleBreedingFeature |
P78622
|
FINISHED |
| Object | pronounced dorsal hump |
—
|
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: pronounced dorsal hump | Statement: [Pink salmon, maleBreedingFeature, pronounced dorsal hump]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maleBreedingFeature Context triple: [Pink salmon, maleBreedingFeature, pronounced dorsal hump]
-
A.
maleFeature
chosen
Indicates that the subject possesses a characteristic or attribute typically associated with males.
-
B.
maleBreedingPlumageFeature
Indicates that the relationship involves a physical or visual characteristic specifically associated with a male’s breeding-season plumage.
-
C.
maleLength
Indicates that the relationship specifies the length or size measurement of a male individual or male part of an entity.
-
D.
reproductiveFeature
Indicates a relationship where an entity possesses or is characterized by a particular reproductive trait, structure, or capability.
-
E.
hornLengthMale
Indicates the measured length of the horns specifically for male individuals in the relationship.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f994b5081908ec02116df654bde |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.