Triple
T25469320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Light |
E638258
|
entity |
| Predicate | universeCreatedBy |
P27680
|
FINISHED |
| Object | Ken MacLeod |
—
|
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: Ken MacLeod | Statement: [Dark Light, universeCreatedBy, Ken MacLeod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeCreatedBy Context triple: [Dark Light, universeCreatedBy, Ken MacLeod]
-
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.
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).
-
D.
inUniverseMaker
Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
-
E.
createdByCharacterInUniverse
Indicates that something (such as a work, object, or concept) was created by a specific character within a particular fictional universe.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f75035a4819090a5301b22743129 |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:21 p.m.