Triple
T26962826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bengalese finch |
E679090
|
entity |
| Predicate | songLearning |
P130143
|
FINISHED |
| Object | learned from tutors |
—
|
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: learned from tutors | Statement: [Bengalese finch, songLearning, learned from tutors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songLearning Context triple: [Bengalese finch, songLearning, learned from tutors]
-
A.
songLearningPeriod
Indicates the time span during which an individual learns or acquires a particular song or vocal pattern.
-
B.
songFunction
Indicates the role or purpose a song serves within a larger context, such as a performance, narrative, or musical structure.
-
C.
learnedMusicFrom
chosen
Indicates that one entity acquired musical knowledge or skills through instruction or influence from another entity.
-
D.
commonlySungTune
Indicates that a particular tune is frequently used as the melody for singing a given piece (such as lyrics, a song, or text).
-
E.
songForm
Indicates the structural pattern or arrangement of sections that defines how a song is organized.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620ede4f88190a98f91af97505663 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:33 a.m.