Triple
T30917293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | That Certain Woman |
E787614
|
entity |
| Predicate | previousVersionTitle |
P2939
|
FINISHED |
| Object | The Transgressor |
—
|
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 Transgressor | Statement: [That Certain Woman, previousVersionTitle, The Transgressor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousVersionTitle Context triple: [That Certain Woman, previousVersionTitle, The Transgressor]
-
A.
previousTitle
chosen
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
-
B.
previousVersionModified
Indicates that a newer version of an entity has been created by modifying the specified previous version.
-
C.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
D.
previousSingleTitle
Indicates that the referenced title is the immediately preceding single released before the current one.
-
E.
previousVersionUsedFrom
Indicates that one entity was used as the immediately preceding version from which another entity was derived or updated.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 29, 2026, 8:51 p.m.