Triple
T19608038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voice of the Animals |
E470655
|
entity |
| Predicate | hasPerformerProfession |
P115040
|
FINISHED |
| Object | musician |
—
|
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: musician | Statement: [Voice of the Animals, hasPerformerProfession, musician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerProfession Context triple: [Voice of the Animals, hasPerformerProfession, musician]
-
A.
hasMainPerformerOccupation
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
-
B.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
C.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
D.
hasMusicalArtistOccupation
chosen
Indicates that an entity has an occupation or professional role as a musical artist.
-
E.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640c964fc8190bd1cb60f4b233eaa |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.