Triple
T23978597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diane Lockhart |
E604442
|
entity |
| Predicate | spinOffLead |
P154105
|
FINISHED |
| Object | The Good Fight |
—
|
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: The Good Fight | Statement: [Diane Lockhart, spinOffLead, The Good Fight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spinOffLead Context triple: [Diane Lockhart, spinOffLead, The Good Fight]
-
A.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
B.
spinOffWork
Indicates that one work is derived from, based on, or created as a spin-off of another preexisting work.
-
C.
helpsLead
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
-
D.
spinOffHelpedInspire
Indicates that the creation or existence of a spin-off contributed to inspiring or motivating something else (such as another work, idea, or development).
-
E.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bba58c8190a1a4b5bcc5bc9d98 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:26 p.m.