Triple
T27138751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Best of Both Worlds |
E681758
|
entity |
| Predicate | realPersonaPerformer |
P86543
|
FINISHED |
| Object | Miley Cyrus |
—
|
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: Miley Cyrus | Statement: [The Best of Both Worlds, realPersonaPerformer, Miley Cyrus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realPersonaPerformer Context triple: [The Best of Both Worlds, realPersonaPerformer, Miley Cyrus]
-
A.
realWorldPerformer
Indicates that an entity serves as the actual, real-world performer of an action, role, or content represented in another entity.
-
B.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
C.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
D.
associatedPerformerPersona
chosen
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6247cdfe88190890ef13287dbdc46 |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:08 a.m.