Triple
T21871795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at the Shoreline |
E540019
|
entity |
| Predicate | includesFormerMemberOf |
P1168
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Live at the Shoreline, includesFormerMemberOf, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFormerMemberOf Context triple: [Live at the Shoreline, includesFormerMemberOf, Yes]
-
A.
formerMemberOf
chosen
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
-
B.
hasNotableFormerMemberRole
Indicates that an entity has a role or position that was notably held by a former member of that entity.
-
C.
hasMemberWhoServedOn
Indicates that a group or organization includes at least one member who has served on a specified body, committee, or entity.
-
D.
hasFormerStaffMember
Indicates that an entity once had a person as a staff member, but that person is no longer employed there.
-
E.
hasHadMemberFromParty
Indicates that an entity (such as an organization or group) has, at some point in time, included at least one member affiliated with a specified political party.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f3368d488190a37224b587858ab0 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:58 p.m.