Triple
T29977343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heather Kidd |
E761484
|
entity |
| Predicate | spouseWorkWith |
P188887
|
FINISHED |
| Object | Elton John |
—
|
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: Elton John | Statement: [Heather Kidd, spouseWorkWith, Elton John]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseWorkWith Context triple: [Heather Kidd, spouseWorkWith, Elton John]
-
A.
spouseInWork
Indicates that two entities are spouses within the context of a particular work (such as a book, film, or series), rather than in real life.
-
B.
hasCollaborativeRoleWithSpouse
Indicates that an individual shares a joint, cooperative role or responsibility together with their spouse.
-
C.
spousePlaceOfWork
Indicates that the place of work specified belongs to the spouse of the referenced person.
-
D.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
-
E.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
- F. None of above. chosen
Provenance (4 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: April 29, 2026, 6:33 p.m.