Triple
T29309491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gigi White |
E743192
|
entity |
| Predicate | spouseNotableCollaboration |
P80466
|
FINISHED |
| Object | John Lennon |
—
|
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: John Lennon | Statement: [Gigi White, spouseNotableCollaboration, John Lennon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseNotableCollaboration Context triple: [Gigi White, spouseNotableCollaboration, John Lennon]
-
A.
spouseNotableWorkField
Indicates that the notable work or professional field associated with a person’s spouse is being specified.
-
B.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
C.
spouse notableWork
Indicates that a person's spouse is significantly associated with a particular notable work.
-
D.
hasCollaborativeRoleWithSpouse
chosen
Indicates that an individual shares a joint, cooperative role or responsibility together with their spouse.
-
E.
spouseNotableWorkLanguage
Indicates that the notable work of a person's spouse is expressed or created in a particular language.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 1:15 p.m.