Triple
T25075829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shards of Honor |
E628044
|
entity |
| Predicate | introducesSeries |
P140701
|
FINISHED |
| Object | Vorkosigan Saga |
—
|
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: Vorkosigan Saga | Statement: [Shards of Honor, introducesSeries, Vorkosigan Saga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesSeries Context triple: [Shards of Honor, introducesSeries, Vorkosigan Saga]
-
A.
introducesSeriesCharacters
Indicates that an entity is responsible for first presenting or bringing specific characters into a series.
-
B.
introducedForSeries
Indicates that an entity was first created or brought into existence specifically for inclusion in a particular series.
-
C.
introducedToSeries
Indicates that one entity caused or enabled another entity to first encounter, become aware of, or start engaging with a particular series.
-
D.
launchesSeries
chosen
Indicates that one entity initiates or starts a sequence or series of related events, actions, or items involving another entity.
-
E.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:21 a.m.