Triple
T26170614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berserker Base |
E654389
|
entity |
| Predicate | hasUniverseCreator |
P27680
|
FINISHED |
| Object | Fred Saberhagen |
—
|
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: Fred Saberhagen | Statement: [Berserker Base, hasUniverseCreator, Fred Saberhagen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUniverseCreator Context triple: [Berserker Base, hasUniverseCreator, Fred Saberhagen]
-
A.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
-
B.
creatorOfUniverse
chosen
Indicates that an entity is responsible for bringing the universe into existence or causing its creation.
-
C.
inUniverseMaker
Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
-
D.
possibleCreator
Indicates that an entity is a plausible but not definitively confirmed creator or originator of another entity.
-
E.
creatorOfInhabitants
Indicates that an entity is the creator or originator of the beings or inhabitants of another entity (such as a place, world, or domain).
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 8:35 p.m.