Triple
T25295780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shangri-Las |
E634213
|
entity |
| Predicate | siblingMembers |
P55387
|
FINISHED |
| Object | Mary Weiss and Betty Weiss |
—
|
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: Mary Weiss and Betty Weiss | Statement: [The Shangri-Las, siblingMembers, Mary Weiss and Betty Weiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siblingMembers Context triple: [The Shangri-Las, siblingMembers, Mary Weiss and Betty Weiss]
-
A.
hasSiblingMembers
chosen
Indicates that two entities are members of a group or organization and are siblings to each other within that membership context.
-
B.
siblingGroup
Indicates that multiple individuals belong to the same set of siblings, sharing at least one parent in common.
-
C.
sibling
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
-
D.
siblingOrRelative
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
E.
siblingBranch
Indicates that two branches share the same immediate parent node in a hierarchical structure, making them parallel or peer branches.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd1d1c08190ba007255d4527a6d |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.