Triple
T27953116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ytse Jam |
E703481
|
entity |
| Predicate | relatedToBandFormerName |
P197791
|
FINISHED |
| Object | Majesty |
—
|
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: Majesty | Statement: [Ytse Jam, relatedToBandFormerName, Majesty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToBandFormerName Context triple: [Ytse Jam, relatedToBandFormerName, Majesty]
-
A.
includesFormerBand
Indicates that one entity currently includes or is composed of a band that previously existed as a separate band.
-
B.
featuresFormerBandMemberOf
Indicates that the subject entity includes, highlights, or presents an individual who was previously a member of the referenced band.
-
C.
hasArtistFormerGroup
Indicates that an artist was previously a member of a particular group or band.
-
D.
formerBandMembership
Indicates that an entity previously belonged to a musical group or band but is no longer a member.
-
E.
relatedBand
chosen
Indicates that two musical groups are connected through some notable association, such as shared members, collaborations, or stylistic/scene affiliation.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: April 27, 2026, 7:26 p.m.