Triple
T28229653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullseye |
E711690
|
entity |
| Predicate | seriesNumberRelative |
P76763
|
FINISHED |
| Object | later installment in the Michael Bennett series |
—
|
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: later installment in the Michael Bennett series | Statement: [Bullseye, seriesNumberRelative, later installment in the Michael Bennett series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesNumberRelative Context triple: [Bullseye, seriesNumberRelative, later installment in the Michael Bennett series]
-
A.
seriesNumberInCarryOn
Indicates that an item has a specific series or sequence number within a set of carry-on items.
-
B.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
C.
reporterSeriesNumber
Indicates the numerical designation of a particular series within a set of reports or reporter publications.
-
D.
hasPartOfSeriesPosition
chosen
Indicates that an entity occupies a specific position or order within a larger series or sequence.
-
E.
seriesVolumeNumber
Indicates the specific volume number assigned to an item within an ordered 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 10:51 p.m.