Triple
T27555064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If I Can’t Love Her |
E695611
|
entity |
| Predicate | musicalAct |
P170649
|
FINISHED |
| Object | Act I |
—
|
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: Act I | Statement: [If I Can’t Love Her, musicalAct, Act I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalAct Context triple: [If I Can’t Love Her, musicalAct, Act I]
-
A.
musicalAssociation
Indicates a relationship where entities are connected through music, such as collaboration, influence, shared performance, or other musically relevant association.
-
B.
performerEnsemble
Indicates a relationship where an individual performer is associated with, or is a member of, a musical or artistic ensemble.
-
C.
performingCompany
Indicates the company that carries out or executes a given performance, production, or event.
-
D.
performingMusicians
Indicates that certain musicians are actively giving a performance, typically in association with a specific event, work, or venue.
-
E.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
- F. None of above. chosen
Provenance (4 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 1:36 p.m.