Triple
T29559380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrible Toybox |
E749996
|
entity |
| Predicate | roleInReturnToMonkeyIsland |
P198876
|
FINISHED |
| Object | co-developer |
—
|
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: co-developer | Statement: [Terrible Toybox, roleInReturnToMonkeyIsland, co-developer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInReturnToMonkeyIsland Context triple: [Terrible Toybox, roleInReturnToMonkeyIsland, co-developer]
-
A.
roleInMacondo
Indicates the specific function, position, or significance an entity holds within the context of Macondo.
-
B.
roleInDonkeyKongCountry
Indicates the specific role or function an entity has within the context of Donkey Kong Country.
-
C.
roleAtLuckyChap
Indicates that an entity holds or held a specific role or position at the organization LuckyChap.
-
D.
roleAtSavoIsland
Indicates the specific role, position, or function an entity held in relation to the event or context associated with Savo Island.
-
E.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: April 28, 2026, 5:18 p.m.