Triple
T35510455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mothership Zeta |
E1026272
|
entity |
| Predicate | locationWithinSeries |
P115815
|
FINISHED |
| Object | Capital Wasteland continuity |
—
|
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: Capital Wasteland continuity | Statement: [Mothership Zeta, locationWithinSeries, Capital Wasteland continuity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationWithinSeries Context triple: [Mothership Zeta, locationWithinSeries, Capital Wasteland continuity]
-
A.
situatedInSeries
Indicates that one entity is located or positioned within a particular series, sequence, or ordered collection of related items.
-
B.
placeInSeries
Indicates the position or order that something occupies within a sequence or series.
-
C.
hasPartOfSeriesPosition
Indicates that an entity occupies a specific position or order within a larger series or sequence.
-
D.
statusWithinSeries
Indicates the position or rank that something holds within an ordered series or sequence.
-
E.
basedInSeries
chosen
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.