Triple
T33209135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Strike |
E850095
|
entity |
| Predicate | hasAuthorWorkSeries |
P159914
|
FINISHED |
| Object | Tales of the South Pacific cycle |
—
|
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: Tales of the South Pacific cycle | Statement: [The Strike, hasAuthorWorkSeries, Tales of the South Pacific cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorWorkSeries Context triple: [The Strike, hasAuthorWorkSeries, Tales of the South Pacific cycle]
-
A.
workInAuthorSeries
chosen
Indicates that a work is part of an author-defined series or collection.
-
B.
relatedWorkSeriesAuthor
Indicates that an author is associated with a work that is part of the same series or a related series as another work.
-
C.
hasAuthorOfOtherWork
Indicates that an entity is the author of another distinct work associated with the first entity.
-
D.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with another entity.
-
E.
hasAuthorOfWorkSetThere
Indicates that the location is a setting in a work created by the specified author.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:30 a.m.