Triple
T26898092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katie Lopez |
E677947
|
entity |
| Predicate | vocalPerformanceIn |
P27956
|
FINISHED |
| Object | Frozen soundtrack |
—
|
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: Frozen soundtrack | Statement: [Katie Lopez, vocalPerformanceIn, Frozen soundtrack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalPerformanceIn Context triple: [Katie Lopez, vocalPerformanceIn, Frozen soundtrack]
-
A.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
B.
vocalPerformanceNotedFor
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
C.
vocalInterpretationOf
Indicates that one entity is a vocal performance or rendition that expresses, realizes, or interprets the content of another entity.
-
D.
performedAsSingerIn
chosen
Indicates that an entity took part in a performance specifically in the role of a singer within a particular event, production, or context.
-
E.
vocalPerformanceReception
Indicates how a vocal performance is received, evaluated, or responded to by an audience, critics, or listeners.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:49 a.m.