Triple
T38357107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethel Merman original Broadway cast recording |
E1046361
|
entity |
| Predicate | recordingOfCharacter |
P47967
|
FINISHED |
| Object | Rose |
—
|
NE NERFINISHED |
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: Rose | Statement: [Ethel Merman original Broadway cast recording, recordingOfCharacter, Rose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingOfCharacter Context triple: [Ethel Merman original Broadway cast recording, recordingOfCharacter, Rose]
-
A.
recordingOf
chosen
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
B.
archiveFootageCharacter
Indicates that a character appears in or is associated with archival footage rather than newly recorded material.
-
C.
characterTypeVoiced
Indicates that one character serves as the voice actor or vocal performer for another character.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
narratedByCharacters
Indicates that the events or content of a work are told or recounted by specific characters within that work.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:31 p.m.