Triple
T32052677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let’s All Sing Like the Birdies Sing |
E818530
|
entity |
| Predicate | performerInAttraction |
P146210
|
FINISHED |
| Object | animatronic birds |
—
|
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: animatronic birds | Statement: [Let’s All Sing Like the Birdies Sing, performerInAttraction, animatronic birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerInAttraction Context triple: [Let’s All Sing Like the Birdies Sing, performerInAttraction, animatronic birds]
-
A.
performerInShow
chosen
Indicates that an entity participates as a performer in a particular show or performance.
-
B.
attractedPerformer
Indicates that one performer feels romantic or sexual attraction toward another performer.
-
C.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
D.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
E.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 12:20 a.m.