Triple
T24455716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back for More |
E616676
|
entity |
| Predicate | recordedByBandLineup |
P139889
|
FINISHED |
| Object | classic 1980s Ratt lineup |
—
|
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: classic 1980s Ratt lineup | Statement: [Back for More, recordedByBandLineup, classic 1980s Ratt lineup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedByBandLineup Context triple: [Back for More, recordedByBandLineup, classic 1980s Ratt lineup]
-
A.
recordedByBandMemberOf
Indicates that a recording was made by an individual who is a member of a specified band.
-
B.
associatedBandLineup
chosen
Indicates that there is a specific band lineup (i.e., configuration of band members) that is linked or connected to the given entity.
-
C.
partOfBandLineup
Indicates that an entity is a member of, or included in, the lineup of a particular band.
-
D.
recordedByFormerMemberOf
Indicates that something (typically a work or performance) was recorded by an individual who was previously, but is no longer, a member of a specified group or organization.
-
E.
bandMemberOnRecording
Indicates that a person is a member of a band who performed on a specific recording.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c5b510819099a92da4c100ded1 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.