Triple
T32744622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pentangle |
E837320
|
entity |
| Predicate | hasOriginalLineupMember |
P153591
|
FINISHED |
| Object | Bert Jansch |
—
|
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: Bert Jansch | Statement: [Pentangle, hasOriginalLineupMember, Bert Jansch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalLineupMember Context triple: [Pentangle, hasOriginalLineupMember, Bert Jansch]
-
A.
originalBandMember
chosen
Indicates that a person was part of the band’s lineup at the time the band was first formed.
-
B.
hasBandMember
Indicates that a musical group includes a specific individual as one of its members.
-
C.
replacedInLineupBy
Indicates that one participant in a lineup is substituted or superseded by another participant in that same lineup.
-
D.
originalTeamMember
Indicates that an entity was part of the initial or founding group associated with another entity (such as a project, organization, or team).
-
E.
hasNotableFormerMemberRole
Indicates that an entity has a role or position that was notably held by a former member of that entity.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 1, 2026, 1:12 a.m.