Triple
T36957281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FormGen |
E914219
|
entity |
| Predicate | roleInWolfenstein3D |
P203700
|
FINISHED |
| Object | retail publisher |
—
|
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: retail publisher | Statement: [FormGen, roleInWolfenstein3D, retail publisher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWolfenstein3D Context triple: [FormGen, roleInWolfenstein3D, retail publisher]
-
A.
roleInInferno
Indicates that one entity has a specific narrative or functional role in relation to another entity within the context of the Inferno.
-
B.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
C.
roleInDishonored
Indicates that an entity holds or plays a particular role within the context of the work titled "Dishonored."
-
D.
roleInCallOfDutyModernWarfare3
Indicates that an entity has a specific role or involvement in the video game "Call of Duty: Modern Warfare 3."
-
E.
roleInDayOfTheTentacle
Indicates that an entity has a specific role or involvement in the game "Day of the Tentacle."
- F. None of above. chosen
Provenance (4 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
| PDg | Predicate description generation | batch_6a01ca0bf57881908d0dcfb2a25556b3 |
completed | May 11, 2026, 12:22 p.m. |
Created at: May 3, 2026, 4:13 p.m.