Triple
T11250006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Fine Productions |
E266299
|
entity |
| Predicate | developed |
P73
|
FINISHED |
| Object | Rad |
E914209
|
NE 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: Rad | Statement: [Double Fine Productions, developed, Rad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rad Context triple: [Double Fine Productions, developed, Rad]
-
A.
Rad
chosen
Rad is a post-apocalyptic 3D roguelike action game by Double Fine Productions featuring a mutating protagonist who gains bizarre powers while exploring a radioactive wasteland.
-
B.
Ra
Ra is the ancient Egyptian sun god, revered as a supreme creator deity and central figure in Pharaonic religion and mythology.
-
C.
RA
RA is a prestigious post-nominal title indicating membership as a Royal Academician of the Royal Academy of Arts in London.
-
D.
RA
RA is the commonly used abbreviation for Rugby Australia, the governing body for rugby union in Australia.
-
E.
RA
RA is the commonly used abbreviation for the Royal Regiment of Artillery, a principal artillery branch of the British Army.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e93212448190b46b3799b0bdfa0f |
completed | April 9, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4f40019588190864c59e8451e80bd |
completed | April 19, 2026, 3:25 p.m. |
Created at: April 8, 2026, 9:31 p.m.