Triple
T5557265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Moon |
E145674
|
entity |
| Predicate | hasWorkInSeriesNumber |
P61667
|
FINISHED |
| Object | seventh Blandings Castle novel |
—
|
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: seventh Blandings Castle novel | Statement: [Full Moon, hasWorkInSeriesNumber, seventh Blandings Castle novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkInSeriesNumber Context triple: [Full Moon, hasWorkInSeriesNumber, seventh Blandings Castle novel]
-
A.
hasWorkInSameSeries
Indicates that two works belong to and are part of the same series.
-
B.
hasSeriesNumber
chosen
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
C.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
D.
sequenceInWork
Indicates that one work appears as a sequential part or installment within a larger overarching work.
-
E.
firstWorkInSeries
Indicates that a work is the initial installment or opening entry in a series or sequence of related works.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ffe12cc81908186f28ace0f4d82 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.