Triple
T27965806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It Could Just Be Love |
E704713
|
entity |
| Predicate | performedByBandType |
P168798
|
FINISHED |
| Object | American rock band |
—
|
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: American rock band | Statement: [It Could Just Be Love, performedByBandType, American rock band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedByBandType Context triple: [It Could Just Be Love, performedByBandType, American rock band]
-
A.
creditedBandType
chosen
Indicates that an entity is credited specifically as a band of a particular type or classification in a given context.
-
B.
playedWithBandFrom
Indicates that an individual has performed as a member or guest with a musical band originating from a specified place or organization.
-
C.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
D.
byBandOrGroup
Indicates that something (such as a work, performance, or recording) is created, performed, or produced by a specific band or musical group.
-
E.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 7:35 p.m.