Triple
T30677780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Swear |
E780966
|
entity |
| Predicate | RBPopVersionPerformer |
P13088
|
FINISHED |
| Object | All-4-One |
—
|
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: All-4-One | Statement: [I Swear, RBPopVersionPerformer, All-4-One]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RBPopVersionPerformer Context triple: [I Swear, RBPopVersionPerformer, All-4-One]
-
A.
revivalVersionPerformer
Indicates that an entity performs or is responsible for a revival version of another entity (such as a work, production, or performance).
-
B.
bestKnownVersionPerformer
chosen
Indicates that the subject is the performer most commonly recognized or associated with the best-known version of the referenced work or piece.
-
C.
romVersion
Indicates the specific ROM (Read-Only Memory) version associated with or used by an entity.
-
D.
vocalGroupVersionOf
Indicates that one work is a vocal-group rendition or arrangement derived from another version of the same musical piece.
-
E.
recordedVersion
Indicates that one entity is a specific recorded version or recording of another entity (such as a work, performance, or composition).
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b19963c81908cf2839cbf1fbf1c |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:32 p.m.