Triple
T5679950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black rhinoceros |
E125175
|
entity |
| Predicate | hornComposition |
P65938
|
FINISHED |
| Object | keratin |
—
|
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: keratin | Statement: [black rhinoceros, hornComposition, keratin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hornComposition Context triple: [black rhinoceros, hornComposition, keratin]
-
A.
coComposer
Indicates a relationship where two or more entities jointly compose a musical or artistic work together.
-
B.
musicComposer
Indicates that one entity is the creator or writer of a piece of music associated with another entity.
-
C.
partOfComposerOeuvre
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
-
D.
compositionChamber
Indicates a relationship where a chamber or enclosed space is used as the setting or environment in which a composition (such as a musical, chemical, or artistic work) is created or formed.
-
E.
musicContribution
Indicates that an entity has contributed in some way to the creation, performance, or production of a musical work.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c0252e18988190a8f3aa0684c12fb8 |
completed | March 22, 2026, 5:21 p.m. |
Created at: March 22, 2026, 3:44 p.m.