Triple
T35967715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red-knobbed curassow |
E1040190
|
entity |
| Predicate | maleDistinctiveFeature |
P78622
|
FINISHED |
| Object | red knob on bill |
—
|
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: red knob on bill | Statement: [red-knobbed curassow, maleDistinctiveFeature, red knob on bill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maleDistinctiveFeature Context triple: [red-knobbed curassow, maleDistinctiveFeature, red knob on bill]
-
A.
maleFeature
chosen
Indicates that the subject possesses a characteristic or attribute typically associated with males.
-
B.
vocalGender
Indicates the perceived or assigned gender associated with an entity’s voice in a vocal performance or recording.
-
C.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
D.
maleCalled
Indicates that a male individual is referred to or named by a particular name or label.
-
E.
maleResembles
Indicates that a male individual bears a notable physical or characteristic similarity to 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.