Triple
T30175431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogglife, Vol. 2: Still Surviving |
E767042
|
entity |
| Predicate | hasSeriesPart |
P194413
|
FINISHED |
| Object | Hogglife, Vol. 1 |
—
|
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: Hogglife, Vol. 1 | Statement: [Hogglife, Vol. 2: Still Surviving, hasSeriesPart, Hogglife, Vol. 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesPart Context triple: [Hogglife, Vol. 2: Still Surviving, hasSeriesPart, Hogglife, Vol. 1]
-
A.
hasPartOfSeriesPosition
Indicates that an entity occupies a specific position or order within a larger series or sequence.
-
B.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
C.
hasSeriesOpus
chosen
Indicates that one work belongs to, or is an installment within, a larger series or opus.
-
D.
partOfSeriesWith
Indicates that one entity is a member or installment within the same series as another entity, linking them as related parts of a larger sequence or collection.
-
E.
hasPartInFilmSeries
Indicates that an entity participates in or contributes to one or more installments within a specific film series.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 29, 2026, 7:25 p.m.