Triple
T26196674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Shack |
E655122
|
entity |
| Predicate | hasNotableMemberLaterKnownAs |
P119824
|
FINISHED |
| Object | Christine McVie |
—
|
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: Christine McVie | Statement: [Chicken Shack, hasNotableMemberLaterKnownAs, Christine McVie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMemberLaterKnownAs Context triple: [Chicken Shack, hasNotableMemberLaterKnownAs, Christine McVie]
-
A.
notableMemberBirthName
Indicates the birth name of a notable member associated with an entity.
-
B.
hasNotableFormerMemberRole
Indicates that an entity has a role or position that was notably held by a former member of that entity.
-
C.
notableMemberCommonName
Indicates that the object is the commonly used or well-known name of a notable member associated with the subject.
-
D.
notableMemberBecame
chosen
Indicates that an individual who is a notable member of one group, organization, or category transitioned into or assumed a role, status, or membership in another.
-
E.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 26, 2026, 8:46 p.m.