Triple
T37041211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Nukem 64 |
E916784
|
entity |
| Predicate | levelDesign |
P98706
|
FINISHED |
| Object | modified levels |
—
|
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: modified levels | Statement: [Duke Nukem 64, levelDesign, modified levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelDesign Context triple: [Duke Nukem 64, levelDesign, modified levels]
-
A.
hasLevelDesign
chosen
Indicates that one entity possesses, is associated with, or is defined by a particular level design created or specified by another entity.
-
B.
levelEditor
Indicates that an entity functions as or is associated with a tool or environment used to create, modify, or arrange levels or stages within a game or application.
-
C.
mapDesigner
Indicates that an entity is the designer or creator responsible for producing a particular map.
-
D.
trackDesigner
Indicates that one entity is the designer or creator responsible for the layout or structure of a track associated with another entity.
-
E.
levelStructure
Indicates that one entity defines or organizes the hierarchical or layered arrangement of 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:14 p.m.