Triple
T35217720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stardeath and White Dwarfs |
E1016860
|
entity |
| Predicate | relativeOfMember |
P206882
|
FINISHED |
| Object | Wayne Coyne |
E1017364
|
NE 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: Wayne Coyne | Statement: [Stardeath and White Dwarfs, relativeOfMember, Wayne Coyne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeOfMember Context triple: [Stardeath and White Dwarfs, relativeOfMember, Wayne Coyne]
-
A.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
formerRelativeOf
Indicates that one entity used to be a relative of another entity, but that familial relationship no longer holds (e.g., due to divorce or legal change).
-
D.
hasRelativeActMember
Indicates that an entity has a relative who is a member of a specified act, group, or organization.
-
E.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
- F. None of above. chosen
Provenance (5 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a38008cf481909bbbc8ec96f393e7 |
completed | June 23, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.