Triple
T36103888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Plotkin |
E1044295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Glulx implementer |
C44758
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Glulx implementer Context triple: [Andrew Plotkin, instanceOf, Glulx implementer]
-
A.
interactive fiction engine
chosen
An interactive fiction engine is a software framework that enables the creation, management, and execution of branching narrative experiences where player choices dynamically influence the story’s progression and outcomes.
-
B.
interactive fiction publisher
An interactive fiction publisher is an entity that selects, develops, and distributes narrative-driven, choice-based digital or print works, often supporting authors with editorial, technical, and marketing resources tailored to interactive storytelling.
-
C.
Lisp machine
A Lisp machine is a specialized computer system designed to efficiently run the Lisp programming language, featuring hardware and software tightly integrated around Lisp’s execution model.
-
D.
Nupoid language
A Nupoid language is a member of a subgroup of the Volta–Niger branch of the Niger-Congo language family, spoken primarily in central Nigeria and characterized by shared phonological and grammatical features.
-
E.
programming language implementation
A programming language implementation is the concrete realization of a language’s specification, including its compiler or interpreter, runtime system, and associated tools that translate and execute programs written in that language.
- F. None of above.
Provenance (1 batch)
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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.