Triple
T37295136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Nukem 3D: 20th Anniversary World Tour |
E925778
|
entity |
| Predicate | voiceActorForDukeNukem |
P185136
|
FINISHED |
| Object | Jon St. John |
—
|
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: Jon St. John | Statement: [Duke Nukem 3D: 20th Anniversary World Tour, voiceActorForDukeNukem, Jon St. John]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceActorForDukeNukem Context triple: [Duke Nukem 3D: 20th Anniversary World Tour, voiceActorForDukeNukem, Jon St. John]
-
A.
voiceActorOfSolidSnake
Indicates that one entity serves as the voice actor for the character Solid Snake in a work.
-
B.
voiceActorMale
Indicates that the subject is a male voice actor who provides the voice for the associated character or role.
-
C.
voiceActorOfPerformer
Indicates that one performer provides the voice for a character or role portrayed by another performer.
-
D.
voiceActorInVideoGames
chosen
Indicates that one entity provides voice acting for a character or role in video games associated with another entity.
-
E.
voiceActorInDishonored2
Indicates that a person served as a voice actor for a character in the video game Dishonored 2.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.