Triple
T32162392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alouatta |
E821461
|
entity |
| Predicate | vocalOrganSpecialization |
P178355
|
FINISHED |
| Object | enlarged hyoid bone |
—
|
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: enlarged hyoid bone | Statement: [Alouatta, vocalOrganSpecialization, enlarged hyoid bone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalOrganSpecialization Context triple: [Alouatta, vocalOrganSpecialization, enlarged hyoid bone]
-
A.
vocalOrgan
Indicates that one entity serves as the vocal organ or sound-producing apparatus of another entity.
-
B.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity or context.
-
C.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
-
D.
vocalTraining
Indicates that one entity provides or engages in training aimed at improving another entity’s vocal or singing abilities.
-
E.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
- F. None of above. chosen
Provenance (4 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: May 1, 2026, 12:32 a.m.