Triple
T4559864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Good Girls Revolt |
E120565
|
entity |
| Predicate | firstRunStatus |
P39416
|
FINISHED |
| Object | canceled after one season |
—
|
LITERAL 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: canceled after one season | Statement: [The Good Girls Revolt, firstRunStatus, canceled after one season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunStatus Context triple: [The Good Girls Revolt, firstRunStatus, canceled after one season]
-
A.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
-
B.
originalRunStatus
chosen
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
C.
firstRunViewership
Indicates the number of viewers who watched a program during its initial (first) broadcast or release.
-
D.
firstModuleLaunch
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
E.
firstPerformedOn
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd582b871c8190be0b70c76d639000 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.