Triple
T23722746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loose Women |
E586187
|
entity |
| Predicate | notableFormerPanellist |
P153712
|
FINISHED |
| Object | Coleen Nolan |
—
|
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: Coleen Nolan | Statement: [Loose Women, notableFormerPanellist, Coleen Nolan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFormerPanellist Context triple: [Loose Women, notableFormerPanellist, Coleen Nolan]
-
A.
notableJuryMember
Indicates that an entity served as a distinguished or noteworthy member of a particular jury or judging panel.
-
B.
notableParticipant
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
C.
notableInterviewee
Indicates that a person has been interviewed by another person or organization in a way considered significant or noteworthy.
-
D.
regularPanelistOn
Indicates that one entity frequently appears as a recurring panel member on a show, program, or discussion forum associated with another entity.
-
E.
notableProponent
Indicates that an entity is a well-known advocate or supporter of another entity, idea, or practice.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b912a7548190afcfa03dd9adc47e |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7:04 p.m.