Triple
T26205767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presence of the Lord |
E655352
|
entity |
| Predicate | hasSupergroup |
P179457
|
FINISHED |
| Object | Blind Faith |
—
|
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: Blind Faith | Statement: [Presence of the Lord, hasSupergroup, Blind Faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupergroup Context triple: [Presence of the Lord, hasSupergroup, Blind Faith]
-
A.
isBySupergroup
Indicates that something (such as a work, event, or item) is created, performed, or produced by a supergroup, i.e., a group formed from members of other established groups.
-
B.
isSupergroupOf
Indicates that one group contains another group as a proper subgroup, having strictly more members or elements than the other.
-
C.
formedSupergroupWith
Indicates that two or more existing musical acts or groups combined their members to create a new collaborative “supergroup.”
-
D.
supergroupFrom
Indicates that one musical group is a supergroup formed from the members or components of another group.
-
E.
supergroupName
Indicates that one entity is the name of a larger group or category (a supergroup) to which another entity belongs.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 26, 2026, 8:50 p.m.