Triple
T22596732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue at the Mizzen |
E574700
|
entity |
| Predicate | finalCompletedWorkInSeries |
P61808
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Blue at the Mizzen, finalCompletedWorkInSeries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalCompletedWorkInSeries Context triple: [Blue at the Mizzen, finalCompletedWorkInSeries, true]
-
A.
finalWorkInSeries
chosen
Indicates that one work is the concluding or last installment within a series of related works.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
completedAfter
Indicates that one event or task was finished at a later time than another specified event or task.
-
D.
workCompletedAfter
Indicates that one entity’s work or task was finished at a later time than another specified work or task.
-
E.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f16269a56881909bb5af0258150f93 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.